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

[Enrico Scholz <enrico dot scholz at informatik dot tu-chemnitz dot de>]

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

From: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/3653: -fmessage-length=72 with g++ makes no sense
Date: 13 Jul 2001 22:23:14 +0200

 Phil Edwards <pedwards@disaster.jaj.com> writes:
 
 > > enrico.scholz@informatik.tu-chemnitz.de writes:
 > > | 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.
 >
 > Many of us with xterms and framebuffer-screens still use 80 columns.
 
 I don't say that the -fmessage-length option shall be removed entirely. I
 say it should be off by *default* because it breaks compatibility and
 reduces readability on screens with more than 80 columns.
 
 
 > (Hint: pieces of paper cannot be stretched.)
 
 Do you really print your error-messages? In some cases it may be usefully
 (e.g. to show colleagues stupid errors and laugh together at them ;) ),
 but then you can use `-fmessage-length=72' explicitly.
 
 (Hint: using a2ps with the -l option produces nice output with more than
 80 columns)
 
 
 
 Enrico