I had some issues with a client where Log4php is installed. He got the error *class LoggerHierarchy not found*, and I found out that, for some reasons, the Autoloader could not load the file.
Unfortunately, as it often happens in production environments, PHP warning were suppressed, therefore nobody realised that the file could not be loaded until I noticed it. I'm therefore asking why the Autoloader uses *include* to load the classes, which simply raises a warning and carries on in case of failure, rather than *require*, which would stop the execution and informing that the file could not be loaded. Personally, I think that *require* should be used, as, if I ask for a class, I need that class and, therefore, the file *must* be loaded for the caller to work properly. Failing silently is not an option, as it simply causes issues later on, making debugging much more difficult. -- View this message in context: http://apache-logging.6191.n7.nabble.com/LoggerAutoloader-Why-include-and-not-require-tp34939.html Sent from the Log4php - Dev mailing list archive at Nabble.com.
