Your skill will accomplish what the force of many cannot |
|
PerlMonks |
Re^2: perltidy block indentationby GrandFather (Saint) |
on Dec 03, 2013 at 13:13 UTC ( [id://1065409]=note: print w/replies, xml ) | Need Help?? |
It doesn't have to be that big a deal. Make the change in one commit with no other code changes. If your existing style is consistent and PerlTidy is tuned well the number of changes will be fairly small in any case. If the number of changes is large that's a clue that your style across the code base is not consistent and may be a good driver for the switch to PerlTidy and enforced consistent style. I've not used git, but I understand it offers very similar tools to Mercurial that would allow you to track changes to a line of interest using the file history. A "cosmetic" change set marked as such in its commit message is easy to ignore. The big win for a team where style matters is that PerlTidy does an excellent job of formatting Perl and provides a great deal of control on exactly how style guides are provided. I use PerlTidy extensively and haven't found a case yet where it has generated broken code from good code. It is likely to work well as part of a pre-commit processing hook for a revision control system to ensure committed code meets team style guides - and that may well be worth the pain of one slightly disruptive commit for a team that has a serious commitment to following their own style guidelines.
True laziness is hard work
In Section
Seekers of Perl Wisdom
|
|