Bug 32299

Summary: Line-wrap in diagnostic-output
Product: [Retired] Red Hat Linux Reporter: Enrico Scholz <rh-bugzilla>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED WONTFIX QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-12-15 14:28:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

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