From mboxrd@z Thu Jan 1 00:00:00 1970 From: Enrico Scholz To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: bootstrap/3653: -fmessage-length=72 with g++ makes no sense Date: Fri, 13 Jul 2001 13:26:00 -0000 Message-id: <20010713202601.30829.qmail@sourceware.cygnus.com> X-SW-Source: 2001-07/msg00391.html List-Id: The following reply was made to PR bootstrap/3653; it has been noted by GNATS. From: Enrico Scholz To: Phil Edwards 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 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