[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:       Erik Sigra <sigra () home ! se>
Date:       2002-02-25 13:33:09
[Download RAW message or body]

tisdagen den 29 januari 2002 19.16 skrev Thiago Macieira:
> Erik Sigra wrote
>
> >Tuesday 29 January 2002 12.24 skrev Kevin Krammer:
> >> >   server.setPort(5678);
> >> >   server.setSocketFlags(KExtendedSocket::passiveSocket);
> >> >   kdDebug() << "server.listen() = " << server.listen() << "\n";
> >> >   connect(&server, SIGNAL(readyRead()), this, SLOT(readData()));
>
> That code has just reminded me of a functionality that is missing from
> KExtendedSocket. The passive sockets (server sockets) don't emit any
> signals when they are ready to accept. I've just written the code (it's
> just a couple of lines), but I'll wait on the status of the CVS before
> committing.

onsdagen den 30 januari 2002 19.58 skrev Thiago Macieira:
> Erik Sigra wrote
> >But "int putch (int ch)" sends an integer. The first byte will contain the
> >intended character and the other 3 bytes will contain garbage, in this
> > case "Ìëÿ" (204, 235, 255). This causes problems at the other end of the
> > connection. My test program had to skip 3 characters after each read.
> > This seems like an annoying bug.
>
> 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).
>
> And, yes, it's supposed to send one character (one byte) only.


Have these things been fixed yet?
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]