> most cases, there aren't very good reasons to throw exceptions from it. How > come you can't declare the class when __autoload() is called but you can do > so later? In such a weird situation, you could declare a proxy object with > the same name which relays all calls to the real class if/when you can load it. > So basically, I understand what you're saying, but I don't see a very > compelling reason to work very hard now to make this work differently.
i`m working on application server for php. i need exception to continue server running after a component couldn`t be found or properly loaded, or at least close it with some trash cleaning. i wanted to write as few code in __autoload as possible, but it seams that i`ll have to check all the possibilities of crashing. rash ps. yes, i know php is supposed to work in a different way than java :] i just love challenges ;) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
