At 00:42 11/22/2002 +0200, Jani Taskinen wrote:
What is so hard to understand in word 'FATAL'?
Fatal what? [1]
+1 on that.If your script doesn't work, what use is it to make it show the cryptic 500 error??
Let's concentrate on the issue:
parse errors belong in 'lint'.
I still think it should be a function, because not only can one verify files, before
'include', but also uploaded php scripts, in some kind of WebDav/CMS environment.
[1] The annoying thing is that FATAL errors can't be handled by an error handler
and can have numerous causes. Same annoying thing as "resource temporarily
unavailable" in CGI environments I'm tracking down at the moment.
I don't like the 500 way either, because you simply loose the entire environment
the bug occured in.
Met vriendelijke groeten / With kind regards,
Webmaster IDG.nl
Melvyn Sopacua
<@Logan> I spent a minute looking at my own code by accident.
<@Logan> I was thinking "What the hell is this guy doing?"
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
