GCC 3.3 Released
devphil writes "The latest version of everyone's favorite compiler, GCC 3.3, was released today. New features, bugfixes, and whatnot, are all available off the linked-to page. (Mirrors already have the tarballs.) Let the second-guessing begin!"
About every GCC release breaks most of the software written for previous version, especially for C++, as it's standard keeps "refining" constantly, as does GCC's interpretation of it. Not to mention the extensions.
Right now I'm busy changing all "#include" to "#include", "friend Foo" to "friend class Foo", and adding "using namespace std" everywhere. What next?
"Only in their dreams can men truly be free 'twas always thus, and always thus will be."
--Tom Schulman
For normal code, yes. For kernel code, maybe. For instance, if you're mucking with the registers, or stack or other non-normal stuff then you may need to ensure that a particular segment of code does not actually make a function call as that would be disastrous.