This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/36150] colorize output of gcc
- From: "brian at dessent dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 May 2008 21:28:56 -0000
- Subject: [Bug other/36150] colorize output of gcc
- References: <bug-36150-14488@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from brian at dessent dot net 2008-05-06 21:28 -------
Subject: Re: colorize output of gcc
esigra at gmail dot com wrote:
> And seriously, what is more efficcent, adding a
> colour code sequence to the string constans in GCC that says "warning:",
> "error:" etc or having a bunch of scripts for parsing the output of various GCC
If you added escape sequences to the string constants in the gcc source
then it would only work for the C locale messages. And isn't your whole
complaint that colorgcc fails for non-C locales? In other words, this
would not do anything in the very case you care about, because in non-C
locales the message strings are taken from the po file and not the
literal strings in the source code.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150