in reply to Tips for dealing with bogus syntax errors

"bogus errors" are often caused by an unclosed string literal or an unbalanced bracket somewhere. Probably the best way to find these is with a syntax-highlighting text editor.

If you're an old dinosaur like me and don't use a syntax-highlighting editor, another way is to just start commenting out blocks of code and running the script through "perl -c". When you comment out the bad line, the error that you're tracking will go away. Then you can comment out progressively smaller blocks of code until you've narrowed the field sufficiently.

  • Comment on Re: Tips for dealing with bogus syntax errors