I once planned to use perltidy to do something similar as part of CPANTS. However, it fell off the bottom of my TODO list. :-)

One of the planned features was to compare the input and output sources using several known styles. This would hopefully give sufficient credit to code that was using a consistent style even if it didn't conform to perltidy's default which is perlstyle. The intention was to provide an objective code metric. Whether, the metric would be useful or not is another debate.

One note, the system call should probably be something like the following for Unix systems:

   system("perltidy $_") == 0
   ...
[download]

--
John.