At least in PHP, you can set a variable in /usr/local/lib/php.ini to
send errors to the web browser which is handy for development. Any of
the two errors below will generate an error message, but things are
complicated if your page uses tables. The bad php code is encountered,
the page generation halts and the table isn't completed and you don't
see an error message!
Test your php application on a simple page before deploying it, if
that's possible!
Or you could run the script from the command line which will generate a
readily available error message :)
Donncha.
"John P . Looney" wrote:
>> I've been using them both a good bit lately. First time ever using them,
> really, for a proper project.
>> And their syntax error reporting leaves a lot to be desired. PHP's the
> worst. Leave out a semi colon, and that whole block of PHP doesn't output
> anything. Leave out a $ before a variable (which, when programming in TCL,
> PHP, Javascript, Bash, SQL, HTML and C in the same day happens a lot), and
> the same thing can happen. Do both, and Gaia help you. If it doesn't
> printout *anything* it should at least tell me why. And line numbers rock.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
