public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de> 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:56:00 -0000 [thread overview] Message-ID: <20010713205602.16986.qmail@sourceware.cygnus.com> (raw) 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:49:22 +0200 Phil Edwards <pedwards@disaster.jaj.com> writes: > On Fri, Jul 13, 2001 at 10:23:14PM +0200, Enrico Scholz wrote: > > say it should be off by *default* because it breaks compatibility > > I really should just resist the impluse to ask, but oh well: > > How does limiting by default to 72 characters /break/ compatibility? Previous gcc versions have not done line-wrapping by default and there are tools relying on an one-line-per-error format (in the maillists I have read the `-fmessage-length=0' was added explicitly to test-scripts and I gave an emacs-example already). It's not the number 72; it's every number between 1 and 1000 (I think error-messages having >1000 columns are exceptions and can be ignored ;)) Enrico
next reply other threads:[~2001-07-13 13:56 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-13 13:56 Enrico Scholz [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-07-16 17:06 Enrico Scholz 2001-07-13 20:36 Gabriel Dos Reis 2001-07-13 17:36 Enrico Scholz 2001-07-13 13:46 Enrico Scholz 2001-07-13 13:36 Phil Edwards 2001-07-13 13:26 Enrico Scholz 2001-07-12 12:56 Phil Edwards 2001-07-12 5:06 Gabriel Dos Reis 2001-07-12 4:06 Enrico Scholz 2001-07-12 1:46 Gabriel Dos Reis 2001-07-11 14:56 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=20010713205602.16986.qmail@sourceware.cygnus.com \ --to=enrico.scholz@informatik.tu-chemnitz.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).