🚀 go-pugleaf

"Stefano Bonifazi" <stefboombastic@email.it> wrote in message
news:464a101b@newsgroups.borland.com...

> I always used Indy SendBuffer and on the other side even
> from Linux they receive fine!

Windows and Linux run on the same hardware architecture, so the endian
is the same.  But if you were to exchange data with to a Mac or other
non-PC machine, the endian would likely not match.  Read/WriteBuffer()
do not perform any endian conversions at all.
Read/WriteInteger/Cardinal/SmallInt(), on the other hand, do perform
conversions from/to network byte ordering by default.  All systems
understand network byte ordering, and the socket API provides
functions (which Indy wraps internally) to convert numbers between
network byte ordering (which is universal across networks) and host
byte ordering (which is specific to the machine being run on).  So,
what you could do is send the individual members of your struct
separately, ie:

    my_struct s;

    TCPClient->WriteBuffer(s.name, 255);
    TCPClient->WriteInteger(s.intnum);
    // and so on...

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

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.

> 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.  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>


Gambit