Re: bootstrap/3653: -fmessage-length=72 with g++ makes no sense

[Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>]

The following reply was made to PR bootstrap/3653; it has been noted by GNATS.

From: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>
To: enrico.scholz@informatik.tu-chemnitz.de
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/3653: -fmessage-length=72 with g++ makes no sense
Date: 12 Jul 2001 10:40:49 +0200

 enrico.scholz@informatik.tu-chemnitz.de writes:
 
 | 1. It breaks existing tools. E.g. Emacs awaits a "<location>:<line>
 | <error-msg>" format and gets confused by the current behavior
 
 My personnal experience (yes, I write and compile my work under
 Emacs) doesn't match your report.  It just works fine.
 
 | 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.
 
 We've through that debate over and over in the past.  The default
 value was what contented the majority which expressed their voices.
 The exact value is configurable.
 
 (And no, I'm not using an xterm)
 
 | 4. Only the g++ frontend defaults to this linebreak. This is inconsequentlally.
 
 That functionality was first implemented for g++.  If you request it
 to be available for other front-ends, I can undertsand that.
 
 If you don't want the fonctionality, the documentation says you can
 specify -fmessage-length=0
 
 -- Gaby