Herold Heiko wrote:
> Unfortunately, on winnt this *is* a problem.
> Visual C 5 does include ctype.h in stdio.h (or something similar, sorry,
> memory is fading).
Is that compliant with the C standard?
> Any idea what would be a sensible way to cover this ?
Instead of:
#ifdef isalpha
#error
#else
...
make a bunch of:
#undef isalpha
#undef isdigit
...
It would be good to have #undefs in one "#ifdef compiler_or_OS_version",
because in general it's possible that isalpha() defined by the compilation
environment doesn't have anything to do with isalpha() defined by the C
language, so in that case throwing #error is the right thing to do.
--
.-. .-. Sarcasm is just one more service we offer.
(_ \ / _)
| [EMAIL PROTECTED]
|