From: Jason Merrill <jason@cygnus.com>
To: Joe Buck <jbuck@Synopsys.COM>
Cc: oliva@dcc.unicamp.br (Alexandre Oliva),
espie@quatramaran.ens.fr, egcs@egcs.cygnus.com
Subject: Re: glossary for egcs - request for contributions
Date: Thu, 29 Apr 1999 21:44:00 -0000 [thread overview]
Message-ID: <u9so9iwwct.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <199904291024.DAA19602@atrus.synopsys.com>
>>>>> Joe Buck <jbuck@Synopsys.COM> writes:
>> > typedef int (*PFDerived)(Derived&);
>> > int bfunc(Base&);
>> > PFDerived p = &bfunc;
>>
>> > this is legal
>>
>> No way! :-)
> Alexandre is right, I was wrong, the C++ language is wrong. (That is,
> they should have permitted contravariance for regular function pointers,
> not just member function pointers).
But then how would you deal with MI? It works for PMFs because they aren't
just pointers.
Jason
WARNING: multiple messages have this Message-ID
From: Jason Merrill <jason@cygnus.com>
To: Joe Buck <jbuck@Synopsys.COM>
Cc: oliva@dcc.unicamp.br (Alexandre Oliva),
espie@quatramaran.ens.fr, egcs@egcs.cygnus.com
Subject: Re: glossary for egcs - request for contributions
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <u9so9iwwct.fsf@yorick.cygnus.com> (raw)
Message-ID: <19990430231500.64_CgzzxNdXlvIskI3yvDTPqn_zgyS5-FCZWuDs8Q2g@z> (raw)
In-Reply-To: <199904291024.DAA19602@atrus.synopsys.com>
>>>>> Joe Buck <jbuck@Synopsys.COM> writes:
>> > typedef int (*PFDerived)(Derived&);
>> > int bfunc(Base&);
>> > PFDerived p = &bfunc;
>>
>> > this is legal
>>
>> No way! :-)
> Alexandre is right, I was wrong, the C++ language is wrong. (That is,
> they should have permitted contravariance for regular function pointers,
> not just member function pointers).
But then how would you deal with MI? It works for PMFs because they aren't
just pointers.
Jason
next prev parent reply other threads:[~1999-04-29 21:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-27 15:24 Philipp Thomas
1999-04-27 22:16 ` Jeffrey A Law
1999-04-28 10:01 ` Theodore Papadopoulo
1999-04-30 23:15 ` Theodore Papadopoulo
1999-04-30 23:15 ` Jeffrey A Law
1999-04-27 23:35 ` Martin v. Loewis
1999-04-28 0:08 ` Joe Buck
1999-04-28 9:46 ` Marc Espie
1999-04-28 23:48 ` Joe Buck
1999-04-29 0:12 ` Alexandre Oliva
1999-04-29 3:26 ` Joe Buck
1999-04-29 3:41 ` Alexandre Oliva
1999-04-30 23:15 ` Alexandre Oliva
1999-04-29 21:44 ` Jason Merrill [this message]
1999-04-30 23:15 ` Jason Merrill
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` Alexandre Oliva
1999-04-29 0:21 ` Jason Merrill
1999-04-30 23:15 ` Jason Merrill
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` Marc Espie
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` Martin v. Loewis
1999-04-30 23:15 ` Philipp Thomas
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=u9so9iwwct.fsf@yorick.cygnus.com \
--to=jason@cygnus.com \
--cc=egcs@egcs.cygnus.com \
--cc=espie@quatramaran.ens.fr \
--cc=jbuck@Synopsys.COM \
--cc=oliva@dcc.unicamp.br \
/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).