[PD] Weird behavior of [moocow/bytes2any], or not?

[Bryan Jurish]

On Thu, Dec 24, 2015 at 10:52 PM, IOhannes m zmölnig <zmoelnig at iem.at>
wrote:

> On 12/24/2015 10:03 PM, Simon Iten wrote:
> > why does readdir on linux output filenames not in order? 16.* before
> 10.* for example?
> most likely because readdir(3) does not return the filenames in the
> order you expect (the order might not be alphabetically but it might be
> sorted by inode number; or creation date; or...).
>
> to cut it short: readdir(3) doesn't guarantee *any* order.
> if some filesystems return data in a given order, that is just by accident.
>
> cf. http://stackoverflow.com/questions/8977441


+1  ... beat me to it ;-)

marmosets,
  Bryan

-- 
Bryan Jurish                           "There is *always* one more bug."
moocow.bovine at gmail.com         -Lubarsky's Law of Cybernetic Entomology
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20151225/98ef202a/attachment.html>