OpenBSD 3.4 isspace() b0rked

[John]

On Mon, Jan 24, 2005 at 04:37:58 +0100, Matthias Andree wrote:
> John <xd890cc2b41c31d74 at f4n.org> writes:
> > 0xa0 in a non-breaking space in ISO 8859-1, so that kind of makes
> > sense, don't know about the rest though. Anyhow, it's bad since it
> > doesn't agree with the docs and the behaviour is unexpected.
> 
> Since when do the C and POSIX locales follow ISO 8859?
What I meant was that OpenBSD can do whatever they wish with their
library, but the docs should always agree with the code. Still, it's a
really bad idea to not conform to the C standard, which reads as their
docs (as posted earlier).

Interestingly enough, POSIX appears to allow inluding extra space
characters (same for upper/lower): 
"In the POSIX locale, at a minimum, the <space>, <form-feed>,
<newline>, <carriage-return>, <tab>, and <vertical-tab> shall be
included."

I believe the reason OpenBSD decided to include extra characters is
their lacking locale support (again, just an ot fyi).