public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: enrico.scholz@informatik.tu-chemnitz.de To: gcc-gnats@gcc.gnu.org Subject: bootstrap/3653: -fmessage-length=72 with g++ makes no sense Date: Wed, 11 Jul 2001 14:56:00 -0000 [thread overview] Message-ID: <20010711215051.10709.qmail@sourceware.cygnus.com> (raw) >Number: 3653 >Category: bootstrap >Synopsis: -fmessage-length=72 with g++ makes no sense >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Jul 11 14:56:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de> >Release: gcc version 3.0.1 20010710 >Organization: >Environment: >Description: By default, g++ assumes -fmessage-length=72. I think this is not a good idea because: 0. Former g++ versions do not do it. Therefore there should be a good reason for the change. 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 is 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. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-07-11 14:56 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-11 14:56 enrico.scholz [this message] 2001-07-12 1:46 Gabriel Dos Reis 2001-07-12 4:06 Enrico Scholz 2001-07-12 5:06 Gabriel Dos Reis 2001-07-12 12:56 Phil Edwards 2001-07-13 13:26 Enrico Scholz 2001-07-13 13:36 Phil Edwards 2001-07-13 13:46 Enrico Scholz 2001-07-13 13:56 Enrico Scholz 2001-07-13 17:36 Enrico Scholz 2001-07-13 20:36 Gabriel Dos Reis 2001-07-16 17:06 Enrico Scholz
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20010711215051.10709.qmail@sourceware.cygnus.com \ --to=enrico.scholz@informatik.tu-chemnitz.de \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).