Xref: utzoo comp.lang.c++:4763 comp.lang.c:22178
Path: utzoo!attcan!uunet!bloom-beacon!usc!gem.mps.ohio-state.edu!apple!well!nagle
From: nagle@well.UUCP (John Nagle)
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: Time to standardize "true" and "false"
Keywords: true false C C++
Message-ID: <13764@well.UUCP>
Date: 22 Sep 89 17:17:23 GMT
References: <13730@well.UUCP> <11126@smoke.BRL.MIL>
Reply-To: nagle@well.UUCP (John Nagle)
Lines: 15

Correction: the definition should have read:
>	enum boolean (false=0, true=1);
     
       Doug Gwin at BRL points out that namespace clashes are a more
general problem in C.  But this isn't a namespace-control problem.
It's not that we want every package to have its own definition of
"boolean", all kept straight in some way and with conversion functions
between package A's "boolean" and package B's "boolean" somehow provided.

       "boolean" really ought to be part of the language, and the logical
operators should return results of type "boolean", but it's too late in
the history of C/C++ for that.  Nevertheless, we should at least have
a consistent definition within the current language structure.

					John Nagle