Re: GNU gcc upgrades

Lawrence MacIntyre <[email protected]>
Newsgroups gmane.linux.usability.annoyances
Organization High Performance Information Infrastructure Group
Message-ID <1064345389.24609.12.camel@nautique>
Versions of g++ previous to 3.0 are VERY different from those from 3.0
and up doe to standards compliance.  Basically any moderately
sophisticated c++ code that was written to the original c++
specification would compile with g++ v2.x but the 3.x compiler will
generate mass quantities of errors and exit if fed the same code.  

On Tue, 2003-09-23 at 14:34, Ian Bruntlett wrote:
> "Jacq, John" <[email protected]> wrote:
> >Hard to ignore if the code doesn't compile at all because of "errors" :^)
> 
> >And yes I am the author more often than not, I still wonder why upgrading 
> >your gcc compiler causes code deemed 100% valid with the previous gcc 
> >version to be suddenly deemed badly lame. Seems kind of strange to me.
> 
> I personally wish I could upgrade gcc but it seems too much of a technical 
> obstacle to me. I like experimenting with C++.
> 
> Could you give more examples - which version of gcc did you upgrade from and 
> which version did you upgrade to? Also, what sort of code snippets suddenly 
> became "lame" after the upgrade? I haven't heard of this sort of thing 
> happening and am really interested.
> 
> 
> Ian
> _______________________________________________
> annoyances mailing list
> [email protected]
> http://michelangelo.renaissoft.com/mailman/listinfo/annoyances
-- 
    Lawrence MacIntyre     865.574.8696     [email protected]
               Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA/cJ8tCNjP8rawCW4RArLcAJ900s6WF8Z74CU9DjmbPskfOMZ78gCeOs5B
ZOEG19GuYE8byXO24NvKE2o=
=n8bZ
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.