Well, my assumption is that the current version of Perltidy should detect the same issues as the old version - missing brackets, especially - and give me an .ERR file.
Since I know the file I'm sending to Tidy has errors because I put them there for testing, I assume I should get an error file.
AND, when I process the file I know has errors through Perl::Critic online, it tells me "perltidy had errors!! at line 1, column 1. See page 33 of PBP. Severity: 1"
Now, I don't know if this is a genuine bug, since when I checked the Perltidy bug report I didn't see anything related to this issue, but when but when four out of the four machines that have had the newest version of Activestate Perl installed on them all have the same issue...
This is the log file for a script I was testing that I know for a fact has a bracket commented out so it would throw an error:
perltidy version 20101217 log file on a MSWin32 system, OLD_PERL_VERSI +ON=5.012002 Windows type is XP/.Net Configuration and command line parameters for this run: -g To find error messages search for 'WARNING' with your editor
In reply to Re^2: perltidy 20101217 not detecting errors
by Dandello
in thread perltidy 20101217 not detecting errors
by Dandello
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |