{ Please remove double-spacing in the quoting. Reformatted. -mod }   
      
   On Friday, May 24, 2013 7:06:11 PM UTC-5, Francis Glassborow wrote:   
   > However there is another issue. The problem is not just endian-ness. C++   
   > specifies very little about fundamental types and that is a deliberate   
   > design decision that has been around since the beginning (and has been   
   > reconsidered and re-affirmed). If different implementations have   
   > different widths for int how will serialisation help in transfer of int   
   > data between programs even given a solution to the endian-ness?   
   >   
      
   Is that something that can be dodged by telling people to   
   use int8_t, int16_t and so on in a marshalling context?  That's   
   what I recommend if I find someone talking about int in that   
   context.  If you're aiming toward portability, I think you have   
   to have clarity about the meaning of the types involved.   
      
      
   Brian   
   Ebenezer Enterprises   
   http://webEbenezer.net   
      
      
   --   
         [ See http://www.gotw.ca/resources/clcm.htm for info about ]   
         [ comp.lang.c++.moderated.    First time posters: Do this! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)