Stanislav Malyshev wrote:
GB>>I meant a logic error - as in the user forgot to use a
GB>>DIRECTORY_SEPARATOR and so can't find any of the classes, not an
GB>>obvious PHP error.
OK - then how exactly you want the error message look like? How the engine
is going to guess if it was DIRECTORY_SEPARATOR missing or the class was
genuinely missing?
GB>>Perhaps a better solution is to simply augment the "undefined class XXX"
GB>>method with a brief listing of all the defined __autoload() functions,
GB>>so the user knows where to look for magic bugs.
What, you mean output all autoloading functions? Why? If you defined them,
you know them, if you didn't, you shouldn't count on them to be there
anyway. And what exactly this listing would reveal to you? You couldn't
find a bug just looking on the names.
Stanislav,
Greg probable means something like a stack trace of the autload callbacks
that were called. This will be a nice addition just like Exception stacktraces
are (I wish there were stacktraces for Fatal errors).
Andrey
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
