🚀 go-pugleaf

In article <1ejy14n.67hdw91ccxccaN%remove.fte@writeme.com>, 
remove.fte@writeme.com (Fabrice Truillot) wrote:

> Rob Barris <rbarris@quicksilver.com> wrote:
> 
> > > Built under CW6 on Windows as a console app, I get the output
> > > 
> > > not less
> > > not less
> > > 
> > > Built under CW6 on MacOS/PPC as a console app, I get this:
> > > 
> > > less
> > > less
> > > 
> > > Who's in the wrong here?
> 
> Try this :
> 
> #include <limits>
> 
> /* some other #include needed */
> 
> int main ()
> {
>     if (numeric_limits<char>::is_signed)
>     {
>         std::cout << "char is signed -> -128 ... + 127"
>                   << std::endl;
>     }
>     else
>     {
>         std::cout << "char is'nt signed -> 0 ... 255"
>                   << std::endl;
>     }
> }
> 


   I'm at home and don't have the Windows compiler handy - but no matter 
what the above reports, the 'chars' in question only assume values of 0 
and 1, in the example posted.  Where it gets into trouble is in 
comparison of such a variable to a constant (not another char, just the 
number 200).

   Clearly either the 'char' should be promoted to int, or the 200 gets 
demoted to char (which would cause the problem I saw on CW/Win) before 
the comparison can take place.  I had always thought that in a case like 
this, the smaller type would get promoted to the larger type and avoid 
this problem.

Rob