Hi Bruno
I just had a look at the code (of the library for HP-NonStop), and it does
indeed look as if they have just been forgotten to get documented and declared
in in dirent.c, here's the code:
int alphasort(struct dirent **d1, struct dirent **d2)
{
return(strcmp((*d1)->d_name, (*d2)->d_name));
}
int alphasort64(struct dirent64 **d1, struct dirent64 **d2)
{
return(strcmp((*d1)->d_name, (*d2)->d_name));
}
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...
Bye, Jojo
-----Original Message-----
From: Joachim Schmitz [mailto:j...@schmitz-digital.de]
Sent: Friday, December 24, 2010 1:57 PM
To: 'Bruno Haible'
Cc: 'bug-gnulib@gnu.org'
Subject: RE: alphasort on HP-NonStop
Thanks.
I'll report this as a bug to HP NonStop development. Last change on the lib was
that scandir() and scandir64() had been added, looks like alphasort() got added
too, but not externalized.
Bye, Jojo
-----Original Message-----
From: Bruno Haible [mailto:br...@clisp.org]
Sent: Friday, December 24, 2010 12:25 PM
To: Joachim Schmitz
Cc: bug-gnulib@gnu.org
Subject: Re: alphasort on HP-NonStop
Joachim Schmitz wrote:
> Ah! Found it in a lib called zutildll! And that indeed gets linked by
> my wrapper script. It is not documented anywhere, so I'm not sure
> whether it serves the purpose POSIX defined for this...
Yes, when a function is not documented, it's most reliable to not use it.
> Not sure whether I'd need to do an #undef HAVE_ALPHASORT or just add
> it's prototype and where to do any of this.
Or set the variable ac_cv_func_alphasort to no in your environment or in a
local config.site file before running configure.
Bruno
