[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KExtendedSocket: putch sends int instead of char
From:       Nicolas Goutte <nicog () snafu ! de>
Date:       2002-01-30 20:26:58
[Download RAW message or body]

If you want to use a QDataStream, it would be the best.

Your idea is unfortunately not endian-safe.

If you do not want to use a QDataStream, please look at this thread of the 
koffice-devel mailing list:
http://lists.kde.org/?t=101094380900037&r=1&w=2

Feel free to ask, if you do not understand something.

Have a nice day/evening/night!

On Wednesday 30 January 2002 20:50, Erik Sigra wrote:
> Wednesday 30 January 2002 19.58 skrev Thiago Macieira:
> > Huh... sorry. My bad. A simple typo caused all that hassle. I've fixed
> > it, but I'll have to wait to commit to CVS (we're right now frozen for
> > the release of beta2).
>
> Good to hear that it will be fixed! Now I just wonder what I have to do
> when I actually want to write an integer?
>
> Should I use "writeBlock(static_cast<char *>(&my_integer), 4)"?
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]