Re: [PHP] debuging and getting mor information about failures

>These errors are usually caused by an extra or missing brace or >quote/apostrophe/backtick. The best way to find where this is happening >is to use another error. Alternatively, use a text editor that's syntax-aware. In bbedit for the mac, finishing a closure or double-clicking on one (parens, b

Re: [PHP] debuging and getting mor information about failures

Yes, you are right. But this depends on your perspective ;) Adam Voigt wrote: Umm, semicolons? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

RE: [PHP] debuging and getting mor information about failures

Peter James on Tuesday, July 29, 2003 9:33 AM said: > Just forwarding this reply back to the list. Damn that Reply button!! Thanks. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] debuging and getting mor information about failures

Umm, semicolons? On Tue, 2003-07-29 at 12:29, Marek Kilimajer wrote: > Check semicommas too. > > Peter James wrote: > > > These errors are usually caused by an extra or missing brace or > > quote/apostrophe/backtick. The best way to find where this is happening is > > to use another error. > >

Re: [PHP] debuging and getting mor information about failures

Check semicommas too. Peter James wrote: These errors are usually caused by an extra or missing brace or quote/apostrophe/backtick. The best way to find where this is happening is to use another error. Start at the bottom of your script and introduce some garbage on a line by itself. "asdf" for

Re: [PHP] debuging and getting mor information about failures

These errors are usually caused by an extra or missing brace or quote/apostrophe/backtick. The best way to find where this is happening is to use another error. Start at the bottom of your script and introduce some garbage on a line by itself. "asdf" for example. This should cause a parse error