X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f Date: Sat, 10 Jan 2004 13:36:48 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp-workers AT delorie DOT com Message-Id: <3405-Sat10Jan2004133647+0200-eliz@elta.co.il> X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <3FFF586F.611F9247@yahoo.com> (message from CBFalconer on Fri, 09 Jan 2004 20:42:07 -0500) Subject: Re: stdbool.h and complex.h References: <3FFCF1F4 DOT B86AC9DA AT yahoo DOT com> <3FFDEB2F DOT F9560613 AT yahoo DOT com> <9003-Fri09Jan2004105245+0200-eliz AT elta DOT co DOT il> <3FFE97BE DOT 4CA94BA3 AT yahoo DOT com> <3FFF2420 DOT 7090305 AT phekda DOT gotadsl DOT co DOT uk> <3FFF586F DOT 611F9247 AT yahoo DOT com> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Fri, 09 Jan 2004 20:42:07 -0500 > From: CBFalconer > > Maybe I've got my head up. This was the line that gave me the > impression that !defined(__STRICT_ANSI__) would let things in. It > uses ||. > > >>>#if (defined(__STDC_VERSION__) && __STDC_VERSION__ >= 199901L) \ > >>> || !defined(__STRICT_ANSI__) That's true: if __STRICT_ANSI__ is not defined, the C9x-style boolean features are exposed. But I don't see what is the problem with that: if the program is not compiled with strict ANSI compliance turned on, we are at liberty to use extensions.