This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/49152] Unhelpful diagnostic for iterator dereference
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 02 Apr 2012 08:16:52 +0000
- Subject: [Bug c++/49152] Unhelpful diagnostic for iterator dereference
- Auto-submitted: auto-generated
- References: <bug-49152-4@http.gcc.gnu.org/bugzilla/>
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?