Hi! >> I'd certainly like it if everything descended from some class (Object? >> StdClass?), but I don't like the idea of an empty construct. As
Making everything descend from the same class may require a number of changes and much bigger design effort than this RFC aims at, with wider BC implications. As for not liking the idea of empty construct - that's too bad since PHP already has it and had it since forever. You just can't call it with parent:: syntax - but you perfectly can use it (not sure you can say "call" since no call is actually happening) with new. >> Anthony pointed out last time, you can't do inheritance and >> simultaneously treat the parent class as a black box. I'm not sure what is meant here. Calling parent ctor is a base OOP technique, everybody does that, it's one of the first best practices people learn when doing OO. Only in PHP, it's weird since you have to know if parent defined ctor or not, and if that changes, patch all your descendant classes. That's just bad OO implementation. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
