Bogus bug??

> > This sample on the bug report is actually a very whittled down version > of where I first experienced the problem. In practice my error class is > loaded on first error and subsequently acts as a singleton. My thoughts > on the problem are that PHP encounters an E_STRICT exception in > testClass.php during the parse, so it invokes the error handler, the > error handler then loads the error class, but because the error itself > occured during the parsing of a class PHP still thinks it's parsing the > class and so when errorClass.php is parsed it fires the fatal error for > class nesting. IMHO that's a parser bug since PHP should (as it normally > does) consider an included/required class description to be outside the > the inclusion scope. > > As an FYI, the reason i use this technique is because my framework uses > a registry type system for modular system services that are lazy loaded, > one of which is the exception service. I guess I missed this problem in > earlier versions of PHP5 because I filter out E_STRICT notices in the > wrapper function that I refuse to correct in my engine for PHP4 > compatibility reasons (I currently filter 3). But it raises the issue > that anytime a new E_STRICT type error is created that I may not have > addressed yet, the result is a fatal error instead of an annoying > E_STRICT :) > > Cheers, > Rob.