perltidy-users

[Jan P. <jp...@gm...>]

Hello,

I am considering the introduction of perltidy as an automated step in
the configuration management process: let it run automatically on
each developer's machine BEFORE each CVS check-in (from Eclipse).

I was wondering whether perltidy has any reliable built-in protection
against modifying the code it was supposed to pretty-print (which
would be catastrophic in the context just described). Is it possible
to test the semantic identity of the code before and after pretty
printing without actually executing it? (For example, by checking
whether it compiles into the exact same Perl bytecode.) If so, does
perltidy contain such a check?

Best regards -
Jan Ploski