https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165
--- Comment #20 from David Malcolm <dmalcolm at gcc dot gnu.org> --- (In reply to Teodor Petrov from 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. > > (After one such complaint I've found this bug, by the way). > > Some suggestions: > Don't pack the line/column info with the file name, if possible. > So the proposed diagnostic from this: > <diagnostic class="error" > location="/home/manuel/src/test/gcc/testsuite/gcc.dg/array-2.c:10:8"> > inicializaci�n de un miembro de matriz flexible en un contexto anidado > </diagnostic> > > will turn in to this, which will be easier to parse: > <diagnostic class="error" > location="/home/manuel/src/test/gcc/testsuite/gcc.dg/array-2.c" line="10" > column="8"> > inicializaci�n de un miembro de matriz flexible en un contexto anidado > </diagnostic> Indeed. > 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. FWIW, in the "firehose" gcc parser, I captured the warning's switch so e.g. "num_get_float.cpp:535:29: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]" has id="string-aliasing" as one of the captured attributes in the XML.
