Re: 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. > > > > 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 when > > encountered. Move this up a few lines at a time, until the original parse > > error goes away, and this one starts. This will help you identify where > > your problem is. > > > > This is a very frustrating error message, but the above should take some of > > the pain away. :-) > > > > HTH. > > Pete. > > -- Adam Voigt (adam@cryptocomm.com) Linux/Unix Network Administrator The Cryptocomm Group