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? -Andrei 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]
- Re: [PHP-DEV] request Jani Taskinen
- [PHP-DEV] R: [PHP-DEV] request Alberto
- Re: [PHP-DEV] request Chuck Hagenbuch
- Re: [PHP-DEV] request Stanislav Malyshev
- Re: [PHP-DEV] request Chuck Hagenbuch
- [PHP-DEV] R: [PHP-DEV] request Alberto
- Re: [PHP-DEV] request Andrei Zmievski
- Re: [PHP-DEV] request Stig Sæther Bakken
- Re: [PHP-DEV] request Andrei Zmievski
- Re: [PHP-DEV] request Chuck Hagenbuch
- Re: [PHP-DEV] request Andrei Zmievski
- Re: [PHP-DEV] request Chuck Hagenbuch
- Re: [PHP-DEV] request Boian Bonev
- Re: [PHP-DEV] request Stig Sæther Bakken
- Re: [PHP-DEV] request Andrei Zmievski
- Re: [PHP-DEV] request Stanislav Malyshev
- Re: [PHP-DEV] request Andrei Zmievski
- Re: [PHP-DEV] request Stanislav Malyshev
- Re: [PHP-DEV] request Stanislav Malyshev
- Re: [PHP-DEV] request Andrei Zmievski
- Re: [PHP-DEV] request Stanislav Malyshev