[MAJOR BUG] g++ 2.95.x generates invalid code for KDE 3.3.0

Matthias Kretz kretz at kde.org
Sun Sep 19 17:39:11 BST 2004

On Sunday 19 September 2004 15:24, Thiago Macieira wrote:
> So, I can come up with a quick-fix: remove the "setBlocking(false)" from
> the constructors. This should, *AFAICS*, workaround the problem. But also
> note that this introduces a behaviour change because KStreamSocket's will
> be blocking by default now. KBufferedSocket may in some occasions report
> that it is blocking when in fact it is not.

Why can't you call the setBlocking at the end of construction (like I showed 
for the testcase you made?). I don't think you should introduce a behaviour 
change, especially not for gcc3 users. If it is really not avoidable, then do 
it in #ifdefs for gcc2 only.

Matthias Kretz (Germany)                          <><
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040919/799a0dda/attachment.sig>

More information about the kde-core-devel mailing list