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

[pinskia at gmail dot com]

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&amp;T
On Apr 2, 2012 4:17, manu at gcc dot gnu.org &lt;gcc-bugzi...@gcc.gnu.org&gt;
wrote: 

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



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

(In reply to comment #30)

&gt; (In reply to comment #26)

&gt; &gt; The caret is not a solution to this problem, because what Gabriel
wants is to

&gt; &gt; not reconstruct expressions ONLY when the caret is shown, but he has
said in

&gt; &gt; the past that the caret should default to OFF to not change the
current output

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

&gt; &gt; back to printing the monsters mentioned above by default.

&gt; 

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

&gt; terminal.

&gt; 



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?