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

[Adriaan de Groot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 22 September 2004 14:39, Stefan Taferner wrote:
> Am Mittwoch, 22. September 2004 14:33 schrieb Leo Savernik:
> > Again? So it was fixed in 2.x and then regressed??

Fer pete's sake, Leo, take off the damn literal hat.

> > Well, it only states that they have no interest/manpower in fixing old
> > releases. But I've never implied that gcc-2.95 should be fixed, but that
> > KDE should refrain from using features that break gcc-2.95. That would be
> > the easier route.
>
> Is it really necessary for Kde to be compilable on 2.95 ?

Yes, since we want to be able to compile and run KDE on Debian systems and 
FreeBSD-STABLE. Not to mention systems where there is no gcc at all and we 
need to watch over portability anyway.

No, since we can always flip the bird at any system which doesn't match the 
tools we happen to use to create KDE. There used to be folks that put time 
into making sure KDE would compile with non-gcc compilers, like the OS/F guy, 
but they seem to have vanished (as an aside, have you ever tried to compile 
KDE with Sun Forte C++? it's stricter than gcc, in particular with function 
pointers taking const arguments, and hence KSSL in particular goes 
_nowhere_). 

- -- 
Don't worry, 't ain't no shame to be stupid - ol' mouse.
    GPG: FEA2 A3FE Adriaan de Groot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBUXYrdqzuAf6io/4RAnEBAJ4/ZkUk8Cvuw/sJyp27Or0r50TTmQCcCktq
uCwwasXOtmI2PrVYezrjNNk=
=NYgq
-----END PGP SIGNATURE-----