Re: [PHP] Parse errors

2012-03-19 Thread tamouse mailing lists
On Sun, Mar 18, 2012 at 2:18 PM, Tim Streater wrote: > On 18 Mar 2012 at 17:46, Simon J Welsh wrote: > >> This is expected. The error doesn't occur to the second file is included, so >> everything in the first included file is parsed and run before execution is >> halted. > > Simon, > > Thanks fo

Re: [PHP] Parse errors

2012-03-18 Thread Tim Streater
On 18 Mar 2012 at 17:46, Simon J Welsh wrote: > This is expected. The error doesn't occur to the second file is included, so > everything in the first included file is parsed and run before execution is > halted. Simon, Thanks for that. Looks like I should be able to catch most places where an

Re: [PHP] Parse errors

2012-03-18 Thread Simon J Welsh
On 19/03/2012, at 6:32 AM, Tim Streater wrote: > After recently omitting a semicolon from the end of a statement, and having > the result be a JavaScript error in an odd place, I'm trying to pin down just > what PHP does with such errors. I made a small test script to run at CLI, > which does s

[PHP] Parse errors

2012-03-18 Thread Tim Streater
After recently omitting a semicolon from the end of a statement, and having the result be a JavaScript error in an odd place, I'm trying to pin down just what PHP does with such errors. I made a small test script to run at CLI, which does some echoes and then, after that, I miss out a semicolon.

Re: [PHP] Parse Errors with 5.2 on Linux

2006-11-07 Thread Robert Cummings
On Tue, 2006-11-07 at 21:18 +, Stut wrote: > Richard Lynch wrote: > > I never have understood why it was kosher to leave the final ?> off, > > for example, so maybe that changed. :-) [I doubt it] > > Certainly hasn't changed, and I hope it never does. Having to find an > errant space or carr

Re: [PHP] Parse Errors with 5.2 on Linux

2006-11-07 Thread Stut
Richard Lynch wrote: I never have understood why it was kosher to leave the final ?> off, for example, so maybe that changed. :-) [I doubt it] Certainly hasn't changed, and I hope it never does. Having to find an errant space or carriage return at the end of an include file that is one of ne

RE: [PHP] Parse Errors with 5.2 on Linux

2006-11-07 Thread Michael Caplan
: Michael Caplan Cc: php-general@lists.php.net Subject: Re: [PHP] Parse Errors with 5.2 on Linux On Tue, November 7, 2006 11:30 am, Michael Caplan wrote: > I just installed PHP 5.2 on a linux server (compiled from source), and > am having some strange problems with a script that is reporting a &

Re: [PHP] Parse Errors with 5.2 on Linux

2006-11-07 Thread Richard Lynch
On Tue, November 7, 2006 11:30 am, Michael Caplan wrote: > I just installed PHP 5.2 on a linux server (compiled from source), and > am having some strange problems with a script that is reporting a > fatal > parse error: > > Parse error: syntax error, unexpected $end in > /xxx/xxx/xxx/functions.php

[PHP] Parse Errors with 5.2 on Linux

2006-11-07 Thread Michael Caplan
Hi there, I just installed PHP 5.2 on a linux server (compiled from source), and am having some strange problems with a script that is reporting a fatal parse error: Parse error: syntax error, unexpected $end in /xxx/xxx/xxx/functions.php on line 1213 This very script parses just a-okay

Re: [PHP] Parse Errors

2002-12-14 Thread DL Neil
Andy, > I am a PHP beginner so this error may be a stupid one. Anyway, I'm > trying to write a simple addition script. The client enters two numbers, > then my script (adder.php) adds them. However, when the script is run, I > get "Parse Error On Line 3" I have no idea exactly what I have done wro

[PHP] Parse Errors

2002-12-14 Thread Andy Turegano
I am a PHP beginner so this error may be a stupid one. Anyway, I'm trying to write a simple addition script. The client enters two numbers, then my script (adder.php) adds them. However, when the script is run, I get "Parse Error On Line 3" I have no idea exactly what I have done wrong. Here is the

[PHP] Parse errors: path?

2002-09-03 Thread Wm
I'm getting a parse error with this PHP statement: $file\n"; } } ?> The browser is showing me the following error though, with a changed path: Parse error: parse error in /usr/local/psa/home/vhosts/.../httpdocs/fashion.php on line 144 That's the only PHP in the entire page, so the error

Re: [PHP] parse errors not displayed (2nd time I ask!)

2002-04-29 Thread 1LT John W. Holmes
To: "php-general" <[EMAIL PROTECTED]> Sent: Monday, April 29, 2002 5:37 PM Subject: [PHP] parse errors not displayed (2nd time I ask!) > *This message was transferred with a trial version of CommuniGate(tm) Pro* > Hi, > > I am sorry I ask this for a second time. > Com

[PHP] parse errors not displayed (2nd time I ask!)

2002-04-29 Thread Pedro Garre
*This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I am sorry I ask this for a second time. Come on guys ! I am sure somebody can help, please I set my own error handler. It is in a file "general_includes.php" (please find it below) and all pages do a "require"