* Drazen Kacar ([EMAIL PROTECTED]) [20010427 00:51]:
I wonder. POSIX compilation environment may not do such a thing with POSIX
headers, unless explicitely allowed by POSIX. I'm too lazy to look into
AFAIK, POSIX is rather useless in this context as it is an ISO issue, with
ctype.h being
From: Philipp Thomas [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 06, 2001 11:02 AM
To: Hrvoje Niksic
Cc: [EMAIL PROTECTED]
Subject: Re: Wget and i18n
* Hrvoje Niksic ([EMAIL PROTECTED]) [20010306 10:35]:
Also, won't this trigger an error if a system header file, say
string.h, happens
Philipp Thomas [EMAIL PROTECTED] writes:
* Herold Heiko ([EMAIL PROTECTED]) [20010426 18:42]:
bugfix), now still ctype.h is included in winnt.h, compilation fails.
(We always knew winnt is an *old* system, but this proves it :).
Any idea what would be a sensible way to cover this ?
Drazen Kacar [EMAIL PROTECTED] writes:
Hm. But that only prevents ctype.h from being included and not the
functions from being used. That's OK, but it's not foolproof.
Right. And it causes problems on machines that include ctype.h
through another header file. Which is why I am strongly
Drazen Kacar [EMAIL PROTECTED] writes:
Hrvoje Niksic wrote:
Drazen Kacar [EMAIL PROTECTED] writes:
Hm. But that only prevents ctype.h from being included and not the
functions from being used. That's OK, but it's not foolproof.
Right. And it causes problems on machines that
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
* Herold Heiko ([EMAIL PROTECTED]) [20010426 18:42]:
bugfix), now still ctype.h is included in winnt.h, compilation fails.
(We always knew winnt is an *old* system, but this proves it :).
Any idea what would be a sensible way to cover this ?
Does MS ctype.h have include guards? If yes, one
Philipp Thomas [EMAIL PROTECTED] writes:
* Hrvoje Niksic ([EMAIL PROTECTED]) [20010305 19:30]:
you leave LC_CTYPE at the default, "C" locale, gettext converts
eight-bit characters to question marks.
What should it do? characters 127 are undefined in LC_CTYPE for
the "C" locale. So
Philipp Thomas [EMAIL PROTECTED] writes:
Ooops, yes my fingers were a bit too fast :-) Here they are, both
safe-ctype.h and safe-ctype.c.
They look good to me. The only thing I don't get is this check:
#ifdef isalpha
#error "safe-ctype.h and ctype.h may not be used simultaneously"
#else
* Hrvoje Niksic ([EMAIL PROTECTED]) [20010306 10:35]:
#ifdef isalpha
#error "safe-ctype.h and ctype.h may not be used simultaneously"
#else
Is the error statement actually true, or is this only a warning that
tries to enforce consistency of the application?
The error statement is
* Hrvoje Niksic ([EMAIL PROTECTED]) [20010306 11:21]:
It is true that old systems use Gcc, but I wonder if anyone tests
*new* Gcc's on old these old systems...
Yes, they do. The patches to make gcc build on the original BSD are only
present in the current CVS GCC.
Philipp
--
Penguins shall
Philipp Thomas [EMAIL PROTECTED] writes:
* Hrvoje Niksic ([EMAIL PROTECTED]) [20010306 11:21]:
It is true that old systems use Gcc, but I wonder if anyone tests
*new* Gcc's on old these old systems...
Yes, they do. The patches to make gcc build on the original BSD are
only present in
* Hrvoje Niksic ([EMAIL PROTECTED]) [20010306 14:09]:
OK, then the #error stays. If noone objects, I'll modify Wget to use
these files.
I have the patches ready and and am about to test them. So if you wait a
bit, you'll get patches ready to apply.
Philipp
--
Penguins shall save the
* Hrvoje Niksic ([EMAIL PROTECTED]) [20010305 18:44]:
Yes. I hate them for making that change, but apparently it's allowed
(or even required, I forget now) by the applicable standards.
It is required. LC_MESSAGES and LC_CTYPE are two different and independent
locale categories.
Philipp,
14 matches
Mail list logo
