[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ambiguous inheritance question

To: Ivan Moore <ivan@cs.man.ac.uk>
Subject: Re: ambiguous inheritance question
From: "Rik Fischer SmOOdy <riks@church>" <riks@church>
Date: Tue, 31 Jan 1995 16:41:44 -0800
Cc: self-interest@self.stanford.edu
In-reply-to: Your message of "Wed, 25 Jan 1995 19:26:16 GMT." <9501251926.AA09847@record.cs.man.ac.uk>
Resent-date: Tue, 31 Jan 1995 16:41:44 -0800
Resent-from: Bay.Chang@Eng.Sun.COM (Bay-Wei Chang [CONTRACTOR])
Resent-message-id: <9502010139.AA12768@traits.Eng.Sun.COM>
Resent-to: real-self-interest@self.stanford.edu

"Experimental" implementations of inheritance (as opposed to Single
Inheritance)  bogged down on this and closely related issues.
I'd suggest avoiding clever heuristics.
If there's any possible ambiguity, make the engineer consciously
resolve it at the time they make the change that causes the ambiguity.

Sufficient cleverness would be to install over riding methods
that cause a "inheritance ambiguity" error.

Rik Fischer Smoody
    smOOdynamics	Systems Made Outa Objects
	2400 NE 25th, Suite 800
	Portland, OR 97212
503-249-8300		riks@cs.pdx.edu

References:
- ambiguous inheritance question
  - From: Ivan Moore <ivan@cs.man.ac.uk>

Prev by Date: Re: ambiguous inheritance question
Next by Date: Re: ambiguous inheritance question
Previous by thread: ambiguous inheritance question
Next by thread: Re: ambiguous inheritance question
Index(es):
- Date
- Thread