[Andrei Zmievski <[EMAIL PROTECTED]>]
> On Sat, 21 Apr 2001, Chuck Hagenbuch wrote:
> > This could result in really confusing and unpredictable behavior if "the first 
> > encountered definition" changed under any circumstances. I'd vote for making 
> > any name conflicts an error.
> You could have two classes both defining an innocent method toString(),
> for example, and with your suggestion, inheriting from those classes
> would cause a hard error? Why would "first encountered" definition
> change?

Okay, what about this one:

If two inherited classes define the same method, the inheriting class
has to redefine it.  This way the inheriting class can be explicit in
how to combine or override the inherited methods.  We'd need a way of
referring to any inherited class's methods though.

 - Stig
  Stig Sæther Bakken <[EMAIL PROTECTED]>
  Fast Search & Transfer ASA, Trondheim, Norway

PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to