public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/8927: Gcc give error for wrong line of C code. Date: Sun, 16 Feb 2003 00:16:00 -0000 [thread overview] Message-ID: <20030216001600.19730.qmail@sources.redhat.com> (raw) The following reply was made to PR c/8927; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.co.uk> To: "Joseph S. Myers" <jsm28@cam.ac.uk> Cc: Steven Bosscher <s.bosscher@student.tudelft.nl>, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gp@qnx.com, Wolfgang Bangerth <bangerth@ticam.utexas.edu> Subject: Re: c/8927: Gcc give error for wrong line of C code. Date: Sun, 16 Feb 2003 00:14:06 +0000 Joseph S. Myers wrote:- > On Sat, 15 Feb 2003, Neil Booth wrote: > > > Too bad the front end separates them. This whole area is currently > > quite messy, and with bison unprofitably hard to fix. The C++ front > > I'll point out again that Bison has built-in support for syntax > productions to have a location as well as a value, although no GCC front > ends currently use it. (It would at least be reasonable for example front > ends such as treelang to make use of this Bison feature.) Hence the use of "unprofitably", which you even referred to in your original mail. We don't want things slower or harder to understand than they already are. Neil.
next reply other threads:[~2003-02-16 0:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-16 0:16 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-16 0:16 Joseph S. Myers 2003-02-16 0:06 Neil Booth 2003-02-15 22:06 Steven Bosscher 2002-12-20 20:54 bangerth
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=20030216001600.19730.qmail@sources.redhat.com \ --to=neil@daikokuya.co.uk \ --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).