🚀 go-pugleaf

Hi Thank U very much!

Remy Lebeau (TeamB) ha scritto:
>     my_struct s;
> 
>     TCPClient->WriteBuffer(s.name, 255);
>     TCPClient->WriteInteger(s.intnum);
>     // and so on...
> 

what I exactly did always :)

>     TCPClient->ReadBuffer(s.name, 255);
>     s.intnum = TCPClient->ReadInteger();
>     // and so on...

Wish they used Indy on Linux..they uses simple Liux socket API.. hope 
they perform conversion from Network endian to Host machine endian as 
well as!!

> 
> Also, you might want to stay away from floating point numbers, if you
> can.  The byte size and binary representation may work differently on
> different hardware architectures as well, regardless of the endian
> used.

Engineering numbers are very seldom integers! .. So what to do?

> 
>> U mean in "advanced compiler" options, "data alignment" right?
> 
> No.  That is a global setting that effects the entire application as a
> whole.  That would be very dangerous and error-prone.  

Oh really?? I wonder why they put the option if that is dangerous!
Thank U!!

What you should
> do instead is wrap your individual structs with #pragma pack
> statements instead, ie:
> 
>     #pragma pack(push, 1)
>     struct my_struct
>     {
>         //...
>     };
>     #pragma pack(pop)
> 
> Or:
> 
>     #include <pshpack1.h>
>     struct my_struct
>     {
>         //...
>     };
>     #include <poppack.h>

Thank U.. never heard about those before!


My best regards!
Stefano B.