From: dewar@gnat.com (Robert Dewar)
To: dewar@gnat.com, fjh@cs.mu.OZ.AU
Cc: gcc@gcc.gnu.org, normanjonas@arcor.de
Subject: Re: Re: c++ "with" keyword
Date: Sat, 18 Jan 2003 07:53:00 -0000 [thread overview]
Message-ID: <20030118003347.A9AC1F2CB2@nile.gnat.com> (raw)
> My viewpoint is slightly different: GCC *should* be used as an arena for
> implementing random language extensions, but in general those extensions
> should not be merged into the main CVS branch. (They would only be merged
> on the main branch if there is a *very* convincing case made for them.)
Yes, of course it is fine to use GCC as an arena for playing with language
extensions. I did not mean to imply otherwise. I was talking about the
official release.
next reply other threads:[~2003-01-18 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 7:53 Robert Dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-04 14:29 Robert Dewar
2003-01-14 14:33 ` Fergus Henderson
2002-12-29 8:32 Norman Jonas
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=20030118003347.A9AC1F2CB2@nile.gnat.com \
--to=dewar@gnat.com \
--cc=fjh@cs.mu.OZ.AU \
--cc=gcc@gcc.gnu.org \
--cc=normanjonas@arcor.de \
/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: link
Be 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).