[Bug c++/49152] Unhelpful diagnostic for iterator dereference

pinskia at gmail dot com gcc-bugzilla@gcc.gnu.org
Mon Apr 2 17:37:00 GMT 2012


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49152

--- Comment #36 from pinskia at gmail dot com <pinskia at gmail dot com> 2012-04-02 17:35:59 UTC ---
I know some of us use tee and that disables termainal detection code usually.
Or output to a file and then use tail -f. So please don't do that. It would
confuse lots of users.



Sent from my Palm Pre on AT&T
On Apr 2, 2012 4:17, manu at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
wrote: 

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49152



--- Comment #31 from Manuel López-Ibáñez <manu at gcc dot gnu.org>
2012-04-02 08:16:52 UTC ---

(In reply to comment #30)

> (In reply to comment #26)

> > The caret is not a solution to this problem, because what Gabriel
wants is to

> > not reconstruct expressions ONLY when the caret is shown, but he has
said in

> > the past that the caret should default to OFF to not change the
current output

> > for IDEs and other software parsing the output of gcc like emacs, so
we are

> > back to printing the monsters mentioned above by default.

> 

> I think I've said before that caret should default to on when the output
is a

> terminal.

> 



Well, that is reassuring. Then, will we still pretty-print expressions in

diagnostics once we have the caret?



Is there a GCC way to detect that the output is a terminal?



More information about the Gcc-bugs mailing list