-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Aug 27, 2018 at 04:32:26PM +0300, Reco wrote: > Hi. > > On Mon, Aug 27, 2018 at 09:08:19AM -0400, Greg Wooledge wrote: > > > Hm. Interfaces man page refers to wordexp(3), but this one doesn't say > > > anything about sorted results > > > > In the absence of such information, the best thing to conclude is that > > the order is unspecified. It may be using the raw unsorted directory > > contents from readdir(3), or it may be starting them all in parallel > > threads, in which case the order will be nondeterministic. > > wordexp(3) invokes glob(3). > > glob(3) states that one *needs* to specify GLOB_NOSORT to get resultes > pathnames in no particular order, as by default the result will be > sorted. > > Unless I'm reading glibc source wrong, the only non-default argument > that wordexp(3) passes to glob(3) is GLOB_NOCHECK.
Thanks for looking into the source. The remaining problem is, since the doc seems pretty fuzzy about that, whether one can rely on this behaviour, or whether this is just an implementation detail which can change under one at any time. Cheers - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAluED2IACgkQBcgs9XrR2kZF+wCdFpzaW8GZDiKF4LxaJp/RJpG7 3VsAnjHEgqjKgjhu2i9pg+ORE3kqyyF/ =8T3S -----END PGP SIGNATURE-----