From: Fergus Henderson <fjh@cs.mu.OZ.AU>
To: Robert Dewar <dewar@gnat.com>
Cc: gcc@gcc.gnu.org, normanjonas@arcor.de
Subject: Re: Re: c++ "with" keyword
Date: Tue, 14 Jan 2003 14:33:00 -0000 [thread overview]
Message-ID: <20030114183333.A24786@hg.cs.mu.OZ.AU> (raw)
In-Reply-To: <20030104142915.3BD6EF2DF9@nile.gnat.com>; from dewar@gnat.com on Sat, Jan 04, 2003 at 09:29:15AM -0500
On 04-Jan-2003, Robert Dewar <dewar@gnat.com> wrote:
> > I think you missed the point. The reason for the with keyword is not to use
> > a pointer but to leave
> > the long structs name which is not done by your example :
>
> My viewpoint here is that gcc should not be used as an arena for
> implementing random language extensions, no matter how meritorious
> they be.
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.)
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
The University of Melbourne | of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.
next prev parent reply other threads:[~2003-01-14 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-04 14:29 Robert Dewar
2003-01-04 15:00 ` Momchil Velikov
2003-01-04 15:24 ` Andrew Haley
2003-01-04 16:25 ` Neil Booth
2003-01-04 17:35 ` Gianni Mariani
2003-01-04 17:59 ` Tolga Dalman
2003-01-04 18:36 ` Gianni Mariani
2003-01-04 18:54 ` Tolga Dalman
2003-01-04 23:32 ` Kevin Handy
2003-01-14 14:33 ` Fergus Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-18 7:53 Robert Dewar
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=20030114183333.A24786@hg.cs.mu.OZ.AU \
--to=fjh@cs.mu.oz.au \
--cc=dewar@gnat.com \
--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).