Stanislav Malyshev wrote:
Depends on the situation. For example, if you autoload with
Zend_Loader a class for which the file does not exist, include_once
emits a warning. If the file exists, and it contains a parse error, it
is not suppressed and the fatal error is handled in the normal PHP
way. It's also possible
I think we can omit (maybe based on configuration) the warning when file
not found, but the error is OK.
that user code contains something that generates other warnings or
errors, and these are neither suppressed nor caught using a custom
error handler.
This is OK too.
I'll then plan to branch Zend_Loader to the incubator with some code to
implement selective suppression of the "file not found" warnings in
autoload().
I'm curious whether the performance cost to production applications will
be deemed worth the benefit, hence my intent to branch to the incubator
for benchmarking comparison with the trunk version. Hopefully the
difference will be negligible for most applications.
Any other opinions?
Best regards,
Darby
