Bug 32299 - Line-wrap in diagnostic-output
Summary: Line-wrap in diagnostic-output
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gcc
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-19 20:40 UTC by Enrico Scholz
Modified: 2007-04-18 16:32 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2002-12-15 14:28:11 UTC


Attachments (Terms of Use)

Description Enrico Scholz 2001-03-19 20:40:05 UTC
By default, g++ assumes -fmessage-length=72. I think this is not a good
idea because:

1. It breaks existing tools. E.g. emacs awaits a "<location>:<line>
<error-msg>" format and gets confused by the current behavior

2. It makes error-messages completely unreadable. E.g. if there are
messages saying something about templates, it's not unusual that the
template-parameter-list is splitted over several lines.

3. The value of 72 is IMHO obsoleted. Are there still existing C++
programmers  which are writing code on an 80-column console? I think most
ones are using xterms or framebuffer-screens with 100 or more columns.

4. Only the g++ frontend defaults to this linebreak. This is
inconsequentlally.

Comment 1 Enrico Scholz 2001-07-11 21:52:12 UTC
Reported upstream (http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3653)

Comment 2 Alan Cox 2002-12-15 14:28:11 UTC
Rejected upstream 


Note You need to log in before you can comment on or make changes to this bug.