|There's more than one way to do things|
Re^2: perltidy 20101217 not detecting errorsby Dandello (Scribe)
|on Feb 07, 2011 at 21:21 UTC||Need Help??|
Just for you, Anonymous
- including an obvious and intentional error.
Run through Perltidy from run/cmd: perltidy -g C:\testing\test.pl
The -g is the flag for a full log including warnings
What I expect: an ERR file from Perltidy telling me I have a missing right curly bracket at or before line 13 and the previous unmatched bracket is at line 10. This file should be in the same directory as the script being checked.
No ERR file and the log is this:
The previous version of Perltidy gave me the ERR file on exactly this type of problem. Now there isn't one. But it still does a nice job prettying up my code.