public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/19165] (Natural) language independent error / warning classification Date: Wed, 30 Jan 2013 18:19:00 -0000 [thread overview] Message-ID: <bug-19165-4-bOqCE1ODZ1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-19165-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165 --- Comment #16 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2013-01-30 18:18:35 UTC --- (In reply to comment #15) > I'm speaking as one of Code::Blocks' developers: > If you implement this we'll for sure use it, because we have many complaints > similar to the one Eclipse's developers have. If you have some developer power to spare, it may be worthwhile to try to tackle this yourself. Otherwise I am afraid this will never be implemented in GCC. The patch in comment #10 is very rough and outdated, but the idea is simple. Copy diagnostic.c to diagnostic-xml.c and start modifying the output functions to emit XML. > Don't pack the line/column info with the file name, if possible. This will be trivial to do. > Also, if it is possible group the notes/instances info with the error/warning > messages. This way it will allows us to show the information in a better way. This will be more complicated, because the diagnostics machinery does not have a concept of multiple messages belonging to the same diagnostic. But I think this is eventually the way to go (and I think Gabriel, the diagnostics maintainer, thinks the same) by the way of defining an internal representation for diagnostics output. (http://gcc.gnu.org/ml/gcc/2012-04/msg00567.html) Dumping this internal representation in XML format would be easy then. But designing and implementing this IR does not seem trivial, so you may want to start with the simple stuff.
next prev parent reply other threads:[~2013-01-30 18:19 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top [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 [this message] 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 [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 2009-08-08 17:05 ` manu at gcc dot gnu dot 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=bug-19165-4-bOqCE1ODZ1@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).