Re: Bytes' order with different C++ compilers

>
> Ok, thanks to everybody for enlightenment. From all this I
> gather that the only thing you are complaining about wrt
> ntoh functions (at least the interface) is argument passed
> by value instead of by ptr to uchar?
>

And just to make sure this horse is dead - one last kick :)
As far as I understand the standard the following should be true:

255 <= UCHAR_MAX <= 2**CHAR_BIT - 1

with both UCHAR_MAX and CHAR_BIT being defined by implementation.

Then shouldn't ****table version be

  uint32value = (( buf[ipos]   & 0xff ) << 24 ) |
                (( buf[ipos+1] & 0xff ) << 16 ) |
                (( buf[ipos+2] & 0xff ) <<  8 ) |
                 ( buf[ipos+3] & 0xff );
instead?

Thanks.
--
 Nikolai

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]