summaryrefslogtreecommitdiffstats
path: root/lib/libc/gen/sem_new.c
diff options
context:
space:
mode:
authorache <ache@FreeBSD.org>2010-01-18 10:17:51 +0000
committerache <ache@FreeBSD.org>2010-01-18 10:17:51 +0000
commit630da6fd8a0f711d519e37a59877d72fce80412c (patch)
tree2cef498b0bfea870dffe17565165756ef03b06fb /lib/libc/gen/sem_new.c
parentcf3f3cdea63c866b330c4caf9f8559ab072f1347 (diff)
downloadFreeBSD-src-630da6fd8a0f711d519e37a59877d72fce80412c.zip
FreeBSD-src-630da6fd8a0f711d519e37a59877d72fce80412c.tar.gz
a) Use strcoll() in opendir() and alphasort() as POSIX 2008 requires.
It also matches now how our 'ls' works for years. b) Remove comment expressed 2 fears: 1) One just simple describe how strcoll() works in _any_ context, not for directories only. Are we plan to remove strcoll() from everything just because it is little more complex than strcmp()? I doubt, and directories give nothing different here. Moreover, strcoll() used in 'ls' for years and nobody complaints yet. 2) Plain wrong statement about undefined strcoll() behaviour. strcoll() always gives predictable results, falling back to strcmp() on any trouble, see strcoll(3). No objections from -current list discussion.
Diffstat (limited to 'lib/libc/gen/sem_new.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud