------- Comment #4 from rob1weld at aol dot com 2009-01-19 18:01 ------- (In reply to comment #3) > Fixed in GCC 4.2.4 and GCC 4.3. I don't think it is worth to fix this in > earlier versions.
Thank you for fixing this. BTW: Between 4.2.1 and 4.2.2 the gcc compiler changed from "supporting old and broken C++ code" to "refusing old and broken C++ code". The result of this change in the compiler was that much of the C++ code on the Internet (even from programming teams at well known Universities) would no longer compile "as-is" and one was required to fix the source that once built without error. In later versions of gcc it got to the point were one could not compile the Linux Kernel since it was gcc (correct) opinion that the code was written too poorly and gcc's arrogance that it was to be unworthy of compiling. You may want to go back to 4.2.1 since it is a different compiler than gcc version 4.2.4 due to the "big break" in the C++ compiler. I keep 3.4.3 (supplied with my OS), 4.2.1, and the Trunk on my system and that way I can compile just about anything without having to do extensive fixups to the C++ code. There was a couple of weeks when 4.2.1 had _most_ of it's "make check" tests pass for all Languages with nearly no FAILs, if you really feel ambitious you might want to check the Testsuite Reports for a particular day that had a revision with the best score. Thanks again for fixing this, it was an annoyance while debugging that portion of the code. Rob -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32754
