[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: alphasort on HP-NonStop
From: |
Paul Eggert |
Subject: |
Re: alphasort on HP-NonStop |
Date: |
Tue, 28 Dec 2010 08:43:44 -0800 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 |
On 12/28/2010 01:59 AM, Joachim Schmitz wrote:
> I see that gnulib uses strcoll() rather than strcmp(), which seems to be what
> POSIX mandates.
> I'll request a bug fix for these issues from HP NonStop development...
When you do that, you might tell them that
there's a possible time bomb there. (I presume
that NonStop developers prefer to avoid time bombs. :-)
If strcoll fails and set errno == EINVAL, then
POSIX allows alphasort to return any value it
likes, which means that if NonStop's qsort requires
a total ordering, their scandir cannot call qsort.
They can avoid the problem either by having a strcoll
that never fails, or by having a qsort that does not
require a total ordering, or by having a scandir that
does not invoke qsort.
- list protocol [was: <signal.h> on HP-NonStop], (continued)
- Re: alphasort on HP-NonStop, Bruno Haible, 2010/12/23
- RE: alphasort on HP-NonStop, Joachim Schmitz, 2010/12/23
- RE: alphasort on HP-NonStop, Joachim Schmitz, 2010/12/24
- Re: alphasort on HP-NonStop, Bruno Haible, 2010/12/24
- RE: alphasort on HP-NonStop, Joachim Schmitz, 2010/12/24
- RE: alphasort on HP-NonStop, Joachim Schmitz, 2010/12/28
- Re: alphasort on HP-NonStop,
Paul Eggert <=
- RE: alphasort on HP-NonStop, Joachim Schmitz, 2010/12/28
- Re: gethostname on HP-NonStop, Bruno Haible, 2010/12/23
- RE: gethostname on HP-NonStop, Joachim Schmitz, 2010/12/23
- RE: gethostname on HP-NonStop, Joachim Schmitz, 2010/12/23
- Re: gethostname on HP-NonStop, Bruno Haible, 2010/12/24
- RE: gethostname on HP-NonStop, Joachim Schmitz, 2010/12/25
- Re: HOST_NAME_MAX on HP-NonStop, Bruno Haible, 2010/12/23
- RE: HOST_NAME_MAX on HP-NonStop, Joachim Schmitz, 2010/12/23
- Re: HOST_NAME_MAX on HP-NonStop, Bruno Haible, 2010/12/24
- RE: HOST_NAME_MAX on HP-NonStop, Joachim Schmitz, 2010/12/25