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


It is commonly the case with technologies that you can get
the best insight about how they work by watching them fail.
                                        -- Neal Stephenson

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