Charles DeRykus <[email protected]> writes:
[...]
> One good sleuthing tool is perltidy (perltidy.sourceforge.net) which is good
> at unraveling a rat's nest of errors to tease out the culprit:
>
> For instance, you'd run: perltidy badlywrittenscript.pl and might get
> an error diagnostic file that'd say something like:
>
> The most recent un-matched '{' is on line 7
> 7: for my $i (@xxx) {
> ^
> 12: To save a full .LOG file rerun with -g
>
Apparently, I'm doing this wrong completely. When I run perltidy
against my albatross it just silently writes albatross.tdy
No commemt at all.
Running with -g flag produces a *.LOG with 290 lines of unintelligable
gibberish ending with:
,----
| First indentation disagreement seen at input line 41
| Last indentation disagreement seen at input line 245
| Note: Indentation disagreement detection is not accurate for outdenting and
-lp.
|
| 14 long lines were outdented:
| First at output line 55
| Last at output line 172
| use -noll to prevent outdenting, -l=n to increase line length
|
| 2 output lines exceeded 80 characters:
| First at line 60 by 10 characters
| Maximum at line 60 by 10 characters
| Last at line 275 by 2 characters
`----
And I can find nothing at those addresses that appears (to me) to be
wrong.
So, just a preliminary test, ... hasn't shown perltidy to be terribly
useful. Probably pilot error in some way.
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
http://learn.perl.org/
