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

Thiago Macieira thiago.macieira at kdemail.net
Sun Sep 19 17:52:41 BST 2004

Matthias Kretz wrote:
>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.

Because it has to be called from the most derived class constructor *only*, 
or after it has finished (i.e., by the user).

If I move the code to KBufferedSocket, then KBufferedSocket cannot be 
further derived. I believe there's code doing that, so it's not a fix.

  Thiago Macieira  -  Registered Linux user #65028
   thiago (AT) macieira (DOT) info
    ICQ UIN: 1967141   PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- 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/425ba078/attachment.sig>

More information about the kde-core-devel mailing list