On 12/24/2015 10:03 PM, Simon Iten wrote: > another moocow question, if you don’t mind… > > why does readdir on linux output filenames not in order? 16.* before 10.* for > example? > on osx and windows i get the expected behaviour. >
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 gfamrds IOhannes
signature.asc
Description: OpenPGP digital signature
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
