In the same spirit (more of an FYI for the OP), 'perldoc perltidy
' does say
Perltidy should work properly on most perl scripts. It does a lot of
self-checking, but still, it is possible that an error could be
introduced and go undetected. Therefore, it is essential to make
careful backups and to test reformatted scripts.
The main current limitation is that perltidy does not scan modules
included with 'use' statements. This makes it necessary to guess the
context of any bare words introduced by such modules. Perltidy has
good guessing algorithms, but they are not infallible. When it must
guess, it leaves a message in the log file.
If you encounter a bug, please report it.
What perltidy does not parse and format
Perltidy indents but does not reformat comments and "qw" quotes.
Perltidy does not in any way modify the contents of here documents
or quoted text, even if they contain source code. (You could,
however, reformat them separately). Perltidy does not format
'format' sections in any way. And, of course, it does not modify pod
|MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"|
|I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).|
|** The third rule of perl club is a statement of fact: pod is sexy.|