Philipp Thomas <[EMAIL PROTECTED]> writes:
> > Is the error statement actually true, or is this only a warning
> > that tries to enforce consistency of the application?
>
> The error statement is true. Remember that ctype.h is locale
> dependent whereas safe-ctype is not. So for instance isprint
> (ctype.h) and ISPRINT (safe-ctype) could well produce different
> results.
But that's a feature. :-) What I was asking was: is the error
statement technically true -- does including ctype somehow harm the
*operation* of safe-ctype?
> And as the intention is to get rid of the locale dependency, you
> have to block the inclusion of ctype.h.
I can easily imagine an application that wants locale processing for
input received by the user, and locale-independent processing for
input received from the wire.
Either way, the question was only to clarify things. I will likely
retain the error to enforce consistency, if nothing else.
> Yes, it would trigger in that case. But safe-ctype was developed for
> GCC originally and as gcc is used also on old systems (one of them
> the original BSD), I guess we would have heard if safe-ctype broke
> things.
It is true that old systems use Gcc, but I wonder if anyone tests
*new* Gcc's on old these old systems...
