Another possibility: could there be a way to add context information (a
string) to the error message the engine displays? This would alleviate
my concern.
Why not just log it into some logfile? Remember that autoloaders can be chained, so engine would have to assemble all strings, display them in order, etc. Why create another mini-logging system?
the point is that if the user is using class_exists() they don't want
extra output on missing class.
But how would you know the class is missing? Maybe next loader in chain would find it. Anyway, this looks like debug feature, why shouldn't it be handled on application level?
--
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com