|There's more than one way to do things|
perltidy 20101217 not detecting errorsby Dandello (Scribe)
|on Feb 07, 2011 at 17:02 UTC||Need Help??|
Dandello has asked for the
wisdom of the Perl Monks concerning the following question:
More of a heads up.
Over the past week I've installed/upgraded Activestate Perl 5.012002 onto three different Windows machines (two Win7 and one XP). The same issue occurs on all three so I can be reasonably sure it's not me since it's a standard install on all three.
Perltidy 20101217 (the one shipped with Activestate Perl 5.012002) is not picking up errors.
These are errors I know are there because I put them there for testing.
Even running with the warning flag doesn't throw errors that I know are there.
I generally run perltidy from the command prompt: perltidy C:\filepathhere
The previous versions of perl and perltidy (about a year old) worked fine.