comment on

Just for you, Anonymous

Input:

#!/usr/bin/perl
use strict;
use warnings;

my $format  = 0;

if ( $format == 1 ) {
 print $format;
}
else {
   print 'Oops';

exit;
[download]

- including an obvious and intentional error.

Run through Perltidy from run/cmd: perltidy -g C:\testing\test.pl

The -g is the flag for a full log including warnings

What I expect: an ERR file from Perltidy telling me I have a missing right curly bracket at or before line 13 and the previous unmatched bracket is at line 10. This file should be in the same directory as the script being checked.

No ERR file and the log is this:

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
[download]

The previous version of Perltidy gave me the ERR file on exactly this type of problem. Now there isn't one. But it still does a nice job prettying up my code.

In reply to Re^2: perltidy 20101217 not detecting errors by Dandello
in thread perltidy 20101217 not detecting errors by Dandello

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks