🚀 go-pugleaf

Stefano Bonifazi wrote:

>My question is: does that work always on every compiler?

Yes, but the results may not be what you want them to be.

> May the 
>procedure of sending that buffer to a program, running on a different 
>OS, produce a different object on destination even by using the same 
>struct type on the second program?

Yes.
See Endian issues.
See also alignment issues.

>  Maybe my problem is silly,and the answer obvious, but I am not sure of 
>what a compiler does exactly allocating data when I create structures 

Depends on the alignment setting.
The default is probably for your char name[255] to be 256 bytes of
storage
Most compilers align the internal items for fast processor access.
So, a compiler for 8086 might default to byte-alignment while one for
pentium would be 4 byte align, and perhaps one for mainframe would be
64 or even 128 bit aligned.
This alignment is overridable by the programmer.

> and what happen to data when sent by Indy or TCP-IP.

It is sent as-is.

Bottom line:
If you are sending exclusively to your own apps, you can do whatever
you want (send raw structures).
If you are sending to someone else's app, or your app that someone
compiles for their harware, you might be better off converting
integers and such into network-endian format and transmit the
individual pieces.


You might Google this group for endian
http://tinyurl.com/28s62e