X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f Message-ID: <400034C9.B3F8281D@yahoo.com> Date: Sat, 10 Jan 2004 12:22:17 -0500 From: CBFalconer Organization: Ched Research X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com 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> <3405-Sat10Jan2004133647+0200-eliz AT elta DOT co DOT il> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Eli Zaretskii wrote: > > > 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. Exactly. The extensions are bool, true, and false. But the file uses _Bool to define bool, which does not exist. The user is not allowed to define _Bool for himself, because it is in the wrong name space. You may have noticed that the substitute file I use for my own purposes defines bool as int, thus avoiding the problem. -- Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net) Available for consulting/temporary embedded and systems. USE worldnet address!