Be the first to post a text review of perltidy. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Tracker comment added

  ptica commented on the turn first block comment in each block into a static one artifact

  posted by ptica 78 days ago

• Tracker artifact added

  ptica created the turn first block comment in each block into a static one artifact

  posted by ptica 78 days ago

• File released: /perltidy/perltidy-20090616/perltidy_20090616-1_all.deb

  posted 202 days ago

• File released: /perltidy/perltidy-20090616/Perl-Tidy-20090616.zip

  posted 202 days ago

• File released: /perltidy/perltidy-20090616/Perl-Tidy-20090616.tar.gz

  posted 202 days ago

• perltidy perltidy-20090616 file released: Perl-Tidy-20090616.zip

  - Allow configuration file to be 'perltidy.ini' for Windows systems. i.e. C:\Documents and Settings\User\perltidy.ini and added documentation for setting configuration file under Windows in man page. - Corrected problem of unwanted semicolons in hash ref within given/when code. - added new flag -cscb or --closing-side-comments-balanced When using closing-side-comments, and the closing-side-comment-maximum-text limit is exceeded, then the comment text must be truncated. Previous versions of perltidy terminate with three dots, and this can still be achieved with -ncscb: perltidy -csc -ncscb } ## end foreach my $foo (sort { $b cmp $a ... However this causes a problem with older editors which cannot recognize comments or are not configured to doso because they cannot "bounce" around in the text correctly. The B<-cscb> flag tries to help them by appending appropriate terminal balancing structure: perltidy -csc -cscb } ## end foreach my $foo (sort { $b cmp $a ... }) Since there is much to be gained and little to be lost by doing this, the default is B<-cscb>. Use B<-ncscb> if you do not want this. - After an isolated closing eval block the continuation indentation will be removed so that the braces line up more like other blocks. OLD: eval { #STUFF; 1; # return true } or do { #handle error }; NEW: eval { #STUFF; 1; # return true } or do { #handle error }; -A new flag -asbl (or --opening-anonymous-sub-brace-on-new-line) has been added to put the opening brace of anonymous sub's on a new line, as in the following snippet: my $code = sub { my $arg = shift; return $arg->(@_); }; This was not possible before because the -sbl flag only applies to named subs. -Fix tokenization bug with the following snippet print 'hi' if { x => 1, }->{x}; which resulted in a semicolon being added after the comma. The workaround was to use -nasc, but this is no longer necessary. -Fixed problem in which an incorrect error message could be triggered by the (unusual) combination of parameters -lp -i=0 -l=2 -ci=0 for example. -A new flag --keep-old-blank-lines=n has been added to give more control over the treatment of old blank lines in a script. The manual has been revised to discuss the new flag and clarify the treatment of old blank lines. Thanks to Oliver Schaefer.

  posted 202 days ago

• perltidy perltidy-20090616 file released: Perl-Tidy-20090616.tar.gz

  - Allow configuration file to be 'perltidy.ini' for Windows systems. i.e. C:\Documents and Settings\User\perltidy.ini and added documentation for setting configuration file under Windows in man page. - Corrected problem of unwanted semicolons in hash ref within given/when code. - added new flag -cscb or --closing-side-comments-balanced When using closing-side-comments, and the closing-side-comment-maximum-text limit is exceeded, then the comment text must be truncated. Previous versions of perltidy terminate with three dots, and this can still be achieved with -ncscb: perltidy -csc -ncscb } ## end foreach my $foo (sort { $b cmp $a ... However this causes a problem with older editors which cannot recognize comments or are not configured to doso because they cannot "bounce" around in the text correctly. The B<-cscb> flag tries to help them by appending appropriate terminal balancing structure: perltidy -csc -cscb } ## end foreach my $foo (sort { $b cmp $a ... }) Since there is much to be gained and little to be lost by doing this, the default is B<-cscb>. Use B<-ncscb> if you do not want this. - After an isolated closing eval block the continuation indentation will be removed so that the braces line up more like other blocks. OLD: eval { #STUFF; 1; # return true } or do { #handle error }; NEW: eval { #STUFF; 1; # return true } or do { #handle error }; -A new flag -asbl (or --opening-anonymous-sub-brace-on-new-line) has been added to put the opening brace of anonymous sub's on a new line, as in the following snippet: my $code = sub { my $arg = shift; return $arg->(@_); }; This was not possible before because the -sbl flag only applies to named subs. -Fix tokenization bug with the following snippet print 'hi' if { x => 1, }->{x}; which resulted in a semicolon being added after the comma. The workaround was to use -nasc, but this is no longer necessary. -Fixed problem in which an incorrect error message could be triggered by the (unusual) combination of parameters -lp -i=0 -l=2 -ci=0 for example. -A new flag --keep-old-blank-lines=n has been added to give more control over the treatment of old blank lines in a script. The manual has been revised to discuss the new flag and clarify the treatment of old blank lines. Thanks to Oliver Schaefer.

  posted 202 days ago

• perltidy perltidy-20090616 file released: perltidy_20090616-1_all.deb

  - Allow configuration file to be 'perltidy.ini' for Windows systems. i.e. C:\Documents and Settings\User\perltidy.ini and added documentation for setting configuration file under Windows in man page. - Corrected problem of unwanted semicolons in hash ref within given/when code. - added new flag -cscb or --closing-side-comments-balanced When using closing-side-comments, and the closing-side-comment-maximum-text limit is exceeded, then the comment text must be truncated. Previous versions of perltidy terminate with three dots, and this can still be achieved with -ncscb: perltidy -csc -ncscb } ## end foreach my $foo (sort { $b cmp $a ... However this causes a problem with older editors which cannot recognize comments or are not configured to doso because they cannot "bounce" around in the text correctly. The B<-cscb> flag tries to help them by appending appropriate terminal balancing structure: perltidy -csc -cscb } ## end foreach my $foo (sort { $b cmp $a ... }) Since there is much to be gained and little to be lost by doing this, the default is B<-cscb>. Use B<-ncscb> if you do not want this. - After an isolated closing eval block the continuation indentation will be removed so that the braces line up more like other blocks. OLD: eval { #STUFF; 1; # return true } or do { #handle error }; NEW: eval { #STUFF; 1; # return true } or do { #handle error }; -A new flag -asbl (or --opening-anonymous-sub-brace-on-new-line) has been added to put the opening brace of anonymous sub's on a new line, as in the following snippet: my $code = sub { my $arg = shift; return $arg->(@_); }; This was not possible before because the -sbl flag only applies to named subs. -Fix tokenization bug with the following snippet print 'hi' if { x => 1, }->{x}; which resulted in a semicolon being added after the comma. The workaround was to use -nasc, but this is no longer necessary. -Fixed problem in which an incorrect error message could be triggered by the (unusual) combination of parameters -lp -i=0 -l=2 -ci=0 for example. -A new flag --keep-old-blank-lines=n has been added to give more control over the treatment of old blank lines in a script. The manual has been revised to discuss the new flag and clarify the treatment of old blank lines. Thanks to Oliver Schaefer.

  posted 202 days ago

• Code committed

  perltidy committed patchset 171 of module perltidy to the perltidy CVS repository, changing 2 files

  posted by perltidy 202 days ago

• Tracker comment added

  Anonymous commented on the unwanted semi-colons inserted in returned hashref artifact

  posted by nobody 259 days ago