X-Authentication-Warning: acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs Date: Tue, 18 May 1999 13:07:24 +0200 (MET DST) From: Hans-Bernhard Broeker X-Sender: broeker AT acp3bf To: Eli Zaretskii cc: djgpp workers list Subject: Re: wctype.h and ctype.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Tue, 18 May 1999, Eli Zaretskii wrote: > On Mon, 17 May 1999, Hans-Bernhard Broeker wrote: > > > > How about including ctype.h from wctype.h? Will that be good enough? > > That's forbidden by the standard, by induction from what I said above. No > > standard header inclusion is allowed to effect inclusion of any other > > standard header. > > Actually, we already do that in several other cases anyway. Do we? I don't remember any such behaviour of the DJGPP ANSI-standard headers, off hand. If we do, it may be time to reconsider this as a possible break of ANSI compatibility. At least in 'gcc -ansi -pedantic' mode, we definitely shouldn't #include any ANSI-standardized header (nor declare the functions it contains, manually). If memory serves, DJ originally put much work in achieving this goal, so I'd be rather surprised if we would have drifted that far away. > > Together, these two clauses mean: standard library function names are only > > reserved *if* you #include the standard header that defines them. > > The question is: why did whoever created wctype.h need to include > ctype.ha in it? No idea. I must not really having followed the begining of this thread that closely. > Does Addendum 1 say something that implies that > including wctype.h pulls in the definitions of is* functions? It most definitely doesn't. At least not as of the latest C9x draft I have. Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.