Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21235
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: Jochem Maas <jochem@iamjochem.com>
Cc: PHP <internals@lists.php.net>
Reply-To: scuzzy@reverseorder.net
Date: Thu, 15 Dec 2005 17:04:06 +0000
Message-ID: <20051215170149.M6855@reverseorder.net>
In-Reply-To: <43A1819B.5090407@iamjochem.com>
References: <20051215121357.M36075@reverseorder.net> <43A1819B.5090407@iamjochem.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=utf-8
Subject: Re: [PHP-DEV] php 5.1.1 syntax errors
From: scuzzy@reverseorder.net ("Daine Mamacos")

I think I know what this is due to.
I have an autoloader in places for classes.
It seems that when a class is autoloaded, no matter what you do, it won't
bother throwing an error when it loads a class. It however just stops
processing. FULL STOP.
If the error is in the localfile, it works fine. runtime errors work fine. It
seems to be pre-runtime errors, now I don't know if this is because of the way
the autoloader works at run time as opposed to pre-runtime.

I don't know.
Anyhow.

If anyone could enlighten me, it would be great.


On Thu, 15 Dec 2005 15:45:47 +0100, Jochem Maas wrote
> 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


--
random signature