in reply to Re^2: perltidy 20101217 not detecting errors
in thread perltidy 20101217 not detecting errors

Aha, now I see. Consulting http://search.cpan.org/dist/Perl-Tidy/CHANGES I see
- added new flag -it=n or --iterations=n This flag causes perltidy to do n complete iterations. For most purposes the default of n=1 should be satisfactory. H +owever n=2
a quick test with -it=2 generates a .ERR file like the previous version used to

You're welcome :)

Replies are listed 'Best First'.
Re^4: perltidy 20101217 not detecting errors
by Dandello (Monk) on Feb 07, 2011 at 23:30 UTC

    Thank You

    Okay - with that flag it does work the way I was expecting/wanted.

    I'm not sure this is a positive change on their part.

    And now there is something searchable for people in the same boat as I was.

      I'm not sure this is a positive change on their part.

      I'm not either, even if there are good reasons for the feature, changing defaults is icky icky icky :)

      Actually, the more I think about it, the more I consider this a bug.

      Actually I'm sure its a bug.

      • It is not documented properly (not in Perl::Tidy).
      • there are no tests for it.
      • I just checked, and this has been the behaviour of Perl-Tidy since 05-Nov-2002. Changing the defaults after 8+ years is just dumb. jswartz was smart enough to add this feature, he should have been smart enough to change his perltidy config file :) and not mess with the defaults

      You should definitely report this :)