[COMMITED][v2] manual: Remove incorrect claim that qsort() can be stabilized
Andreas Schwab
schwab@suse.de
Thu Dec 11 09:39:00 GMT 2014
Paul Eggert <eggert@cs.ucla.edu> writes:
> The last clause is incorrect. C11 and POSIX both require that the
> addresses passed to the comparison function must point to elements of the
> original array, and glibc qsort conforms to the standards here.
That is only true for bsearch:
"The comparison function pointed to by compar is called with two
arguments that point to the key object and to an array element, in
that order."
The description for qsort does not say that:
"The contents of the array are sorted into ascending order according
to a comparison function pointed to by compar, which is called with
two arguments that point to the objects being compared."
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
More information about the Libc-alpha
mailing list