public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/19165] (Natural) language independent error / warning classification
Date: Sat, 08 Aug 2009 16:33:00 -0000 [thread overview]
Message-ID: <20090808163320.31945.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19165-6458@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from joseph at codesourcery dot com 2009-08-08 16:33 -------
Subject: Re: (Natural) language independent error / warning
classification
On Sat, 8 Aug 2009, manu at gcc dot gnu dot org wrote:
> I am not planning to work on this further. This patch shows that it can be
> done, but I don't know if there is any interest on this.
The principle makes sense (obviously the prototype patch would need
further work for actual inclusion, e.g. escaping of < and > signs for the
XML output), but I think in practice it's only useful if driven by
cooperation from IDE people who will help establish what the XML should
look like and commit to making an IDE use the XML output in future by
default when using a GCC version that supports it.
I imagine that the XML should have some way of marking continuation
messages as such, should include the option (as from
-fdiagnostics-show-option) in some structured way, and probably should
give locations and inclusion context in an XML structured way as well
rather than as plain text - but discussion would be needed with IDE people
on what information GCC can give and how an IDE could use it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165
next prev parent reply other threads:[~2009-08-08 16:33 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
2009-08-08 16:06 ` manu at gcc dot gnu dot org
2009-08-08 16:33 ` joseph at codesourcery dot com [this message]
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=20090808163320.31945.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).