Wez Furlong wrote:
It's generally a bad idea, and definitely something to avoid if you are building a class library.
You have now been warned that the traffic is dangerous; if you want to go play in it, it's your choice :-)
The same could be said for using an external Framework or library (except that they'd have the luxury of protecting important methods with "final").
I take it parent::method() works with built-in classes?
err Wez do you think this should really be the case? This will make the idea that further levels of abstraction be implemented in userland kinda needlessly hard. This will mean that you need to wrap rather than extend. Or let me rephrase: I would very much appreciate it if an explicit extra effort (triple E) would be made to prevent these kind of situations. Obviously as new functionality is added there might be issues. Then again atleast we two dont seem to have a large overlap in method naming :-)
regards, Lukas
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
