This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: mp = &o.f;
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 18 March 2003 6:04 pm, Joe inspired the electrons to say:
> > > > The refering URL is:
> > > > http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2002/n1384.pdf
>
> I wrote:
> > > That document makes three proposals. The first one, bound pointers to
> > > members, I would heartily support, as it would greatly simplify a lot
> > > of the code that I (and others) write....
> > > ...
> > > It might make sense for GCC to accept clean implementations of serious
> > > standard-extension proposals, but we'd need to be very cautious about
> > > it...
>
> On Tue, Mar 18, 2003 at 05:17:04AM +0100, Christian Parpart wrote:
> > What exactly does this now mean to the possible implementation of (at
> > least) the bound pointers to members in g++?
>
> At least two things would need to happen: first, a motivated person would
> need to contribute a patch that implements the feature in a minimally
> disruptive manner (against the CVS trunk, not the current release).
> Second, the C++ front end maintainers would need to approve it. There
> would be some reluctance to implement an extension, but less so if it is a
> formal proposal to the standards committee that is seen as having some
> chance of being accepted.
>
> Proposals that others do work generally aren't greeted with much
> enthusiasm. Good contributions, though, that is another matter.
Hi,
well I unfortunately can't put my time into this patch because I'm not familar
with the gcc internals, that is, the sources, its design model, etc. I now
tried it at least twice to look deeper into it, but it's not really funny to
read it. I'd really like to patch it myself, but the time does not allow me
to introduce me into the gcc code :(
Where are the C++ parser maintainers when not on this list (because they
probably just didn't read this mail)?
It may be that they're lots of times faster than me in implementing this......
Best regards,
Christian Parpart
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+d91gPpa2GmDVhK0RApXSAJ9Li/7L4npHYHyWpQ+AilGeedqlmwCfWSFi
07L6DoNHPOwkmGegp2RpNUo=
=9y/g
-----END PGP SIGNATURE-----