[FX.php List] Suggestions on finding parse errors in long PHP pages

[Jonathan Schwartz]

Bob,

This is always a lot of fun.

If the error isn't on the line number offered, then we are talking 
missing "}" in a if statement, no?

If so, I use the latest version of BBEDIT that offers the ability to 
visually see in the Margin, the symbols indicating opening and 
closing if statements.  Although it doesn't wave at you, it is just a 
matter to narrow down the location of the mssing closing bracket.

Not sure if that is the issue for you.  HTH.

If you find a more intelligent method, I'd love to hear.

Jonathan


At 12:21 PM -0600 11/28/07, Bob Patin wrote:
>I have a form that has embedded PHP all the way down, on approx. 40 
>survey questions; now that I managed to get to the bottom of the 
>form and test it, I'm getting a parse error.
>
>The problem is that the error msg. lists a line that isn't relevant 
>to the actual lines of the code; do you guys have a way to take the 
>parse error line # and interpolate it so that it shows the actual 
>error line?
>
>Thanks,
>
>Bob Patin

-- 
Jonathan Schwartz
Exit 445 Group
jonathan at exit445.com
http://www.exit445.com
415-381-1852