Why would this be the case? PHP is server-side and client independent...
-Original Message-
Your problem is undoubtably to do with the difference in line
endings on
mac/pc/unix.
This message is
Ed,
Read the rest of the email. The problem WASN'T to do with what CLIENT was
reading the page at the time, it was to do with what SERVER was running the
PHP code.
Saving his text files onto the Mac, and then trying to run them produced
Error on line 1, whilst saving and running the code on
Perhaps it was a typo, but parse error on line 1 does state the line
number.
tyler
On Tue, 2002-06-18 at 09:57, Kevin Ruiz wrote:
I'm running php 4 on a unix server and am experiencing a problem with error
reporting I'm getting on my mac.
When I get a parse error it won't tell me what line
Kevin,
This can either be set dynamically by the error_reporting() function, or
changed in the php.ini file.
http://www.php.net/manual/en/function.error-reporting.php
http://www.php.net/manual/en/features.error-handling.php
Best regards,
Andrew Hill
Director of Technology Evangelism
OpenLink
I'm sorry...I think I was unclear.
Even if my script has an error on say line 42 it still tells me that the
error is on line 1. I've done some debugging and now that there's only one
error on the page but it always tells me that the error is on line 1.
Thanks.
in article
Your problem is undoubtably to do with the difference in line endings on
mac/pc/unix.
Basically, when PHP parses your file, it see's it all as one line, and is
finding the error on LINE 1, which is correct.
When the same file is saved on a unix or pc system, the line endings are
different, and
i've seen this quite often and in my case, it always happens when you
have en error in an if or similar sentence. then it always tells me
theres an error on line 1 (ie 5.2 on mac os x).
chris
Am Dienstag den, 18. Juni 2002, um 17:12, schrieb Kevin Ruiz:
I'm sorry...I think I was unclear.
7 matches
Mail list logo
