Hello Arne, yep, those are the tricky parts. I would pea for having final respected. For private we need to investigate further.
marcus Wednesday, October 3, 2007, 4:21:40 PM, you wrote: > On Wed, 2007-10-03 at 07:24 +0200, Sebastian Bergmann wrote: >> Stanislav Malyshev schrieb: >> > Thanks, will look at these. I'm extremely uncomfortable with engine >> > change that would allow "new Foo" produce an object that is not Foo. >> >> The restriction >> >> "A class may only pose as one of its direct or indirect superclasses." >> >> I mentioned ensures that "new Foo" can only produce objects that are in >> an is_a relationship with Foo. > That will conflict with your previous statement, that one can "override" > final classes. And it will cause serious trouble with anything marked > private in the original class. Or won't it? > CYA Arne Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
