internals,
it may be a badly worded (and inappropriately directed) post BUT I can
categorically
say that php5+ does have problems with displaying errors under certain
circumstances - you see nothing anywhere regardless of ini/log/display settings.
I have had such issues since php.5.0.3beta, I have never been able to
reproduce the issue in a simple script (certain degree of code complexity is
required - in practice that means running a 'production' framework of some
sort).
examples of the sort of problems that cause NOTHING to be reported, NOTHING to
be
logged and NOTHING to be displayed:
1. failed require/require_once statements.
2. non-abstract class with abstract methods (as declared in a base class).
3. method signature incompatibilities.
when faced with such an error (like I just spent another 2 hours figuring out
a newly developed class was missing a method [no. 2] - not the first time!) the
only recourse I have it to start at the first line of php that is run and
write something like:
die("WTF IS GOING ON!?!?! :-(");
and then keep moving it a line or 2 down at a time (stepping into
all/any include files, of which there are normally about 25-50) until
I find the offending line/file (at which point I can try to figure out
what is actually wrong).
Daine Mamacos wrote:
Is there any reason why the php 5.1.1 command processor does not report syntax
errors despite all errors being on in the .ini file?
Maybe I'm doing something stupid.
mee too - wish I knew what it was.
--
random signature
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
