Slashdot Mirror
GCC 3.0.4 is Out
Isle writes: "GCC 3.0.4 has finally been released.
As those who has tried the prereleases will know this version finally compiles a working version of aRts and thus compiles the entire KDE-suite. With the Linux kernel compiling already with the 3.0.3 version, gcc 3.0 now compiles all major projects I know of.
Is it finally time to dump that good old 2.95?"
Is also out now and according to the changelog, it finally works with gcc 3.
FreeSpeech.org
- optimizations in the dynamic linker. binaries created by recent binutils versions start up quicker due to reduced time spend on relocations.
If I am reading this correctly, this is the much talked-about fix for the long startup times of KDE programs.Yay
I use the --subnodes option and pipe through less to get a more usable printout. The info program has a really crappy interface.
like this:
info --subnodes bison | more
If tits were wings it'd be flying around.
There are a couple C++ features that nobody implements because they're too esoteric to put people on. There are a few C++ features that nobody implements because they're too hard to get into the compiler. Most compilers do the core set of features pretty well at this point. It's to the point where 95% of the spec and 99.99% of the spec that people actually use works just about anywhere.
:), then it's probably a bit better than VS C but nothing out there is going to be much better.
Later versions of VS C have been getting more standards compliant for these core features. Check the documentation as VS C defaults to maintining backward compatibility (like K&R block variable scoping) over standards compliance in some respects. GCC has a few of the lesser used features that VS C does not. It shouldn't matter what backend you're compiling towards for supporting these features in GCC. VS C still does not do good templates although nobody does even great templates.
However, GCC thought it would be wonderful to add new features to C++ and so there are a bunch of programs locked into using GCC because they use GCC proprietary extensions. In that sense, I'd say GCC is much less standards compliant than VS C. If you are careful about avoiding the GCC extensions (or just disable them
By the way, you shouldn't try and use things like BOOST as a metric. As they say on their page:
"Warning: These tables are not a good indication of a particular compiler's compliance with the C++ Standard."
It's because a lot of code has either platform workarounds that hide bugs or proprietary extensions (like GCC's) that cause bugs on certain compilers.
The STL has an exception to the GPL:
// As a special exception, you may use this file as part of a free software
// library without restriction. Specifically, if other files instantiate
// templates or use macros or inline functions from this file, or you compile
// this file and link it with other files to produce an executable, this
// file does not by itself cause the resulting executable to be covered by
// the GNU General Public License. This exception does not however
// invalidate any other reasons why the executable file might be covered by
// the GNU General Public License.
So you can use any license for C++ programs.
...but RMS won't let us.
There are days when I dream about another GCC fork.
You cannot apply a technological solution to a sociological problem. (Edwards' Law)