Hi,
I agree with Danīs opinion.
Watching from a point of view of a developer working on PHP Object Oriented aplications, libs, frameworks, etc, there is no sense on things like this. Or it IS object oriented or it IS NOT. Partiality always run into complications. And that was what happen on PHP4, where OO (although good) was the art of "workarounds"...
There is no such thing as object oriented or not. All OO languages differ. In Java for example, you have to include (import) any class you want to use (unless you are using reflection). __autoload() gives you a shortcut which relieves you from having to include each and every class definition you want to use. But this comes with rules, and the rule is, that if you fail to create the class definition in __autoload() it's a fatal error. I really don't want to discuss this anymore because it's been discussed in the past, and reasons have been given. I've written some sample code lately with __autoload() and I must say it's a dream not having to include all these classes :)
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
