Re: [PHP4BETA] calling member in parent class

At 00:45 05/02/2000 , Matthew Hixson wrote:

On Fri, 04 Feb 2000, Zeev Suraski wrote: Why? It's a matter of a trivial search&replace, it's not as if it's a big dael... It depends upon how big your codebase is whether its a big deal or not. For a project with multiple developers working on many files this is more than a trivial search and replace. For even small, one man projects I think this would be a great addition. Is there a good reason _not_ to do it? If you don't want to use it, noone's forcing you...

Well, generally, every feature should have a very good reason before it's added to a language. It's not the other way around - if there's no reason not to add it, add it. There's always a reason not to add it - to keep the language simpler and less cluttered with built-in language level functionality. But that was a general comment. Regardless of your code size, PHP allows you to have a class definition at the scope of a single file, and a single file only. That means that no matter how big your code is, changing the inherited class name, for a given derived class, is exactly one search&replace. So it boils down to this difference - a replacement of the parent class name in the 'extends' statement, vs. a single search and replace. No noticeable difference in my book... Finally, as I said, we might add a special notation for this in the future. As it's absolutely no necessary, we don't plan on doing this in the near future (Zend is feature-frozen for 4.0, and I really mean it this time :). Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/