From: Jason Merrill <jason@cygnus.com>
To: allen@eecs.tulane.edu (Joshua S. Allen), egcs@cygnus.com
Subject: Re: Multiple inheritance
Date: Mon, 01 Dec 1997 18:46:00 -0000 [thread overview]
Message-ID: <u9en3wcx0d.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <199712011505.JAA11781.cygnus.egcs@duvieux.eecs.tulane.edu>
>>>>> Joshua S Allen <allen@eecs.tulane.edu> writes:
> I am making modifications to the gnu g++ compiler to include automatic
> conflict resolution of multiple inheritance using a linearization
> algorithm.
What do you mean?
> (1) I need to construct a table of direct parents of a class. Whereas this
> could easily be done at parse time, it is presenting me with problems and I
> was wondering if you could direct me to how this information could be
> extracted from the parse tree.
TYPE_BINFO_BASETYPES (type) is a vector of the direct bases.
> (2) I am adding the algorithm within the function lookup_fnfields
> (cp/search.c) where
> errstr = "request for method %D' is ambiguous";
> Once I locate the method in a class, what is the format of the return
> value I give to the calling function. I need a way of telling the calling
> function the particular method within a specific class to use.
lookup_fnfields returns a list where the PURPOSE is the basetype where the
functions are found, and the VALUE is the list of functions.
Jason
next parent reply other threads:[~1997-12-01 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199712011505.JAA11781.cygnus.egcs@duvieux.eecs.tulane.edu>
1997-12-01 18:46 ` Jason Merrill [this message]
1997-12-10 16:00 Mike Stump
-- strict thread matches above, loose matches on Subject: below --
1997-12-02 22:54 Mike Stump
1997-12-10 7:31 ` Joshua S. Allen
1997-12-01 7:05 Joshua S. Allen
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=u9en3wcx0d.fsf@yorick.cygnus.com \
--to=jason@cygnus.com \
--cc=allen@eecs.tulane.edu \
--cc=egcs@cygnus.com \
/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).