Preserved Topic: Debugging PHP (Page 1 of 1)

Every time I have an error in a PHP script, the page returns a parsing error at line 1 regardless of where the error actually is? Is there some way to configure PHP to return the actual line #?

Must say it's always given me the right number I don't think there's any config issue there.

Are you using your semi-colons?
The only time I get something like this is if I forget a semi-colon


Walking the Earth like Kane

Well should it say that if you have a semi-colon missing on say the 20th line? I've managed to debug the script, and the problem was a missing semi-colon, and I can't remember if I had any other errors. I didn't see any reason that it wouldn't be able to tell which line was missing a semi-colon.

Any time I get an error (Lord knows that's often), it returns the right line number. It's probably like Bitdamaged said, maybe you didn't close a statement properly. If that's the case, the line number returned with the error, will be the line where PHP thinks the statement starts.

Well after weeks of debugging my scripts by commenting out new sections then adding them one line at a time, I finally figured out what is wrong. Thought it might help someone else some day.

Simply put, PHP judges line numbers not by semi-colons, but by Unix linefeeds. Having edited my files on a Mac, it all appeared to be one line to PHP. Fortunately BBEdit lets you save in Unix format.