in reply to Tips for dealing with bogus syntax errors

Even without posting the whole code, are you able to reproduce the same behaviour in the fewest lines of code as possible?

Also, you could try to run your script with strict and warnings on:

perl > 5.6+
perl -Tc -Mstrict -Mwarnings -Mdiagnostics file.pl
perl < 5.6
perl -Twc -Mstrict file.pl
And see what it does.
Note also that perl generated syntax errors are really seldomly bogus! :)

Cheers,
OeufMayo, live from HAL2001

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

Replies are listed 'Best First'.
Re: Re: Tips for dealing with bogus syntax errors
by rucker (Scribe) on Aug 11, 2001 at 02:47 UTC
    Unfortunately your tips don't help in this instance. I can't reproduce the behavior from scratch, and I've only seen it happen with this one project. I've used perl enough to know that it seldomly generates bogus errors. If it often did, I wouldn't be asking this question because I'd already know the "secrets" ;) This reminds me of times using gcc when it would locate an error in whatever.h, when there was a syntax error in another previously included .h. (Maybe I'm just dense.)