public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/19165] (Natural) language independent error / warning classification
Date: Mon, 22 Jan 2007 16:12:00 -0000 [thread overview]
Message-ID: <20070122161202.17472.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19165-6458@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from tromey at gcc dot gnu dot org 2007-01-22 16:12 -------
Some kind of machine-readable output is necessary for use by an IDE.
Eclipse can't translate the messages after they have been emitted by GCC.
So, it should run GCC in the user's locale.
However, then it would like to differentiate between warnings and errors.
There's no way to do that without knowing all the ways that GCC might
translate the words "warning" and "error" (running in a locale Eclipse
thinks it understands is not a good option because GCC may change its
choices of translation...). It would be friendlier if
GCC provided this information. XML, or anything machine-readable, would be
fine.
So, yes, this is a GCC bug.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165
next prev parent reply other threads:[~2007-01-22 16:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19165-6458@http.gcc.gnu.org/bugzilla/>
2005-10-23 6:47 ` tromey at gcc dot gnu dot org
2006-05-15 18:42 ` ttimo at idsoftware dot com
2007-01-22 8:59 ` manu at gcc dot gnu dot org
2007-01-22 16:12 ` tromey at gcc dot gnu dot org [this message]
2009-08-08 16:06 ` manu at gcc dot gnu dot org
2009-08-08 16:33 ` joseph at codesourcery dot com
2009-08-08 17:05 ` manu at gcc dot gnu dot org
[not found] <bug-19165-4@http.gcc.gnu.org/bugzilla/>
2012-11-15 10:39 ` manu at gcc dot gnu.org
2012-11-15 15:32 ` clemens1509 at web dot de
2013-01-30 12:14 ` fuscated at gmail dot com
2013-01-30 18:19 ` manu at gcc dot gnu.org
2013-01-30 20:34 ` fuscated at gmail dot com
2013-03-27 0:59 ` manu at gcc dot gnu.org
2021-08-24 9:50 ` pinskia at gcc dot gnu.org
2004-12-27 14:22 [Bug other/19165] New: " walles at mailblocks dot com
2004-12-27 14:29 ` [Bug other/19165] " pinskia at gcc dot gnu dot org
2004-12-27 17:51 ` walles at mailblocks dot com
2005-03-29 1:46 ` pinskia at gcc dot gnu dot org
2005-03-29 8:04 ` walles at mailblocks dot com
2005-07-15 21:22 ` pinskia at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070122161202.17472.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).