🚀 go-pugleaf

In Article<3vo825$k9n@engnews2.Eng.Sun.COM>, <clamage@Eng.Sun.COM> write:
 
> For compatibility with existing code during the transition period, you can
> place something like the following in a project header file:
> 
>     #ifdef NO_BOOL_TYPE
> 	typedef int bool; // allows implicit conversions but not overloading
> 	const bool false = 0;
> 	const bool true = 1;
>     #endif
> 
> and then #define NO_BOOL_TYPE for compilers which do not yet support bool.
> An alternative, which does not allow implicit conversions but which does
> allow overloading on bool would be
> 
> 	enum bool { false, true };
> 
> ---
> Steve Clamage, stephen.clamage@eng.sun.com
> 
> 

An alternitive that would allow both overloading and implicit type
conversions is something like this:

enum BOOLEAN { false, true };

class bool {
   BOOLEAN value;
public:
    // Put in type conversion, operators, etc.
}

Granted, it takes two identifiers, but I think it comes closest to
implementing the type as the draft standard does (at least among
what I've seen so far).

Trebor A. Rude
trebor@en.ecn.purdue.edu