------- Comment #7 from manu at gcc dot gnu dot org 2008-05-07 10:06 ------- (In reply to comment #6) > Colorization of a message is part of the message. It should obviously be done > whereever the message is constructed. (IDE has nothing to do with this.) With > your argument, the compiler should not do text messages (or any localization > thereof) either, but rather return some code that an external program > formats/localizes and presents to the user in a suitable way.
Actually, that doesn't sound too bad. It will probably help to embed GCC in IDEs and other customizations. But I digress... Adding color output (ala ls --color) or the proposal in this bug (gcc as a lecturer in programming) show a critical misunderstanding: Assuming that GCC developers are bored and have nothing to do. There are many many features that GCC developers themselves would like to see implemented and they are not because of lack of time. Therefore, people coming up with random half-backed ideas, which they do not intend to fully specify, much less implement, is hopeless. Honestly, GCC is free software. Anyone can implement whatever they want. We gave you our reasons why we think this is a bad idea. Prove us wrong by writing the code (or finding someone to write it for you). If it is indeed a good idea, distributions and users will pick it up and that will show that developers should change their minds and include it in the original source code. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31983
