Warp wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> I'm merely 
>> pointing out that the errors you describe comes from treating "int"s as 
>> "integers". There's no such thing as an "unsigned integer", only an 
>> "unsigned int".  It was a nit, nothing more. :-)
> 
>   I didn't understand that.

The C declaration of
   unsigned int X;
does not allocate an integer variable.

You wouldn't need signed/unsigned conversion rules if you were working 
with integers instead of int's.

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?

Post a reply to this message