🚀 go-pugleaf

Hi all!:)
  In short I would like to send whole structure instances by using 
TCP-IP.. for example through Indy TCPClient.
The first and secure way is to serialize the members of a structure in a 
buffer and then send them with

procedure WriteBuffer(const ABuffer; AByteCount: Longint; const 
AWriteNow: boolean);

Anyway for simple structures for example:

struct
{
  char name[255];
  int intnum;
  float fnum;
} my_struct;

it seems to work even something like that:

WriteBuffer (&myStruct,sizeof(my_struct));

that means that in memory they are simply placed one right the other.. 
so on the other side I can receive the buffer by knowing that structure 
size, and cast the buffer to that struct pointer!

My question is: does that work always on every compiler? 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?

  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 or 
classes, and what happen to data when sent by Indy or TCP-IP.

Thank U very much in advance,
Stefano B.