From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: mxu@cae.wisc.edu
Cc: gcc@gcc.gnu.org
Subject: Re: "self" constructor
Date: Thu, 23 Mar 2000 09:21:00 -0000 [thread overview]
Message-ID: <200003231708.SAA00781@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <38DA2B93.D84DA3D9@cae.wisc.edu>
> In addition, as a user of gcc, I wish this feature can be put into
> the compile as a "extension". That's why I send this question to
> this email list. Is there any wishes list for gcc?
No particular list. The gcc list is probably best. Please also have a
look
http://gcc.gnu.org/cgi-bin/fom.cgi?file=12
I think it is unlikely that option 2 will bring you anywhere, so
you'll have to consider option 1 and option 3.
I personally think it would be a bad thing to have such an extension,
and will take no further steps in making that happen. In fact, I will
argue against it should a patch be provided.
Regards,
Martin
next prev parent reply other threads:[~2000-03-23 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-22 17:22 Min Xu
2000-03-22 17:53 ` Alexandre Oliva
2000-03-23 0:59 ` Martin v. Loewis
2000-03-23 6:35 ` Min Xu
2000-03-23 9:21 ` Martin v. Loewis [this message]
2000-03-22 19:07 Mike Stump
2000-03-23 6:40 ` Min Xu
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=200003231708.SAA00781@loewis.home.cs.tu-berlin.de \
--to=martin@loewis.home.cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=mxu@cae.wisc.edu \
/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).