Next | Query returned 56 messages, browsing 1 to 10 | Previous

History of commit frequency

CVS Commit History:


   2023-08-03 09:13:23 by Wen Heping | Files touched by this commit (2) | Package updated
Log message:
Update to 20230701

Upstream changes:
## 2023 07 01

    - Issue git #121. Added parameters -xbt, or --extended-block-tightness,
      and -xbtl=s, or --extended-block-tightness-list=s, to allow
      certain small code blocks to have internal spacing controlled by
      -bbt=n rather than -bt=n. The man pages have details.

    - Issue git #118. A warning will be issued if a duplicate format-skipping
      starting marker is seen within a format-skipping section. The same
      applies to duplicate code-skipping starting markers within code-skipping
      sections.

    - Issue git #116. A new flag --valign-if-unless, -viu, was added to
      allow postfix 'unless' terms to align with postfix 'if' terms.  The
      default remains not to do this.

    - Fixed git #115. In the two most recent CPAN releases, when the
      Perl::Tidy module was called with the source pointing to a file,
      but no destination specified, the output went to the standard
      output instead of to a file with extension ``.tdy``, as it should
      have.  This has been fixed.

    - Fixed git #110, add missing documentation for new options
      -cpb and -bfvt=n. These work in version 20230309 but the pod
      documentation was missing and has been added.

    - Fixed an undefined reference message when running with
      --dump-block-summary on a file without any subs or other
      selected block types.

    - Add parameter -ipc, or --ignore-perlcritic-comments.  Perltidy, by
      default, will look for side comments beginning with ``## no critic`` and
      ignore their lengths when making line break decisions, even if the user
      has not set ``-iscl``.  The reason is that an unwanted line break can
      make these special comments ineffective in controlling ``perlcritic``.
      The parameter -ipc can be set if, for some reason, this is not wanted.

    - Some minor issues with continuation indentation have been fixed.
      Most scripts will remain unchanged.  The main change is that block
      comments which occur just before a closing brace, bracket or paren
      now have an indentation which is independent of the existance of
      an optional comma or semicolon.  Previously, adding or deleting
      an optional trailing comma could cause their indentation to jump.
      Also, indentation of comments within ternary statements has been
      improved. For additonal details see:

      https://github.com/perltidy/perltidy/blob/master/docs/ci_update.md

    - This version was stress-tested for many cpu hours with random
      input parameters. No failures to converge, internal fault checks,
      undefined variable references or other irregularities were seen.

    - This version runs several percent faster than the previous release
      on large files.
   2023-07-06 11:43:03 by Thomas Klausner | Files touched by this commit (2483)
Log message:
*: recursive bump for perl 5.38
   2023-04-30 00:55:13 by Wen Heping | Files touched by this commit (2)
Log message:
Update to 20230309

Upstream changelog is too long, please visit:
https://metacpan.org/dist/Perl-Tidy/changes
   2022-06-28 13:38:00 by Thomas Klausner | Files touched by this commit (3952)
Log message:
*: recursive bump for perl 5.36
   2022-04-30 05:05:54 by Wen Heping | Files touched by this commit (2)
Log message:
Update to 20220217

Upstream changelog is too long, please visit:
https://metacpan.org/dist/Perl-Tidy/changes
   2021-11-07 01:15:13 by Wen Heping | Files touched by this commit (2) | Package updated
Log message:
Update to 20211029

Upstream changes:
## 2021 10 29

    - No significant bugs have been found since the last release, but several
      minor issues have been fixed.  Vertical alignment has been improved for
      lists of call args which are not contained within parens (next item).

    - Vertical alignment of function calls without parens has been improved with
      the goal of making vertical alignment essentially the same with or
      without parens around the call args.  Some examples:

        # OLD
        mkTextConfig $c, $x, $y, -anchor => 'se', $color;
        mkTextConfig $c, $x + 30, $y, -anchor => 's',  $color;
        mkTextConfig $c, $x + 60, $y, -anchor => 'sw', $color;
        mkTextConfig $c, $x, $y + 30, -anchor => 'e', $color;

        # NEW
        mkTextConfig $c, $x,      $y,      -anchor => 'se', $color;
        mkTextConfig $c, $x + 30, $y,      -anchor => 's',  $color;
        mkTextConfig $c, $x + 60, $y,      -anchor => 'sw', $color;
        mkTextConfig $c, $x,      $y + 30, -anchor => 'e',  $color;

        # OLD
        is id_2obj($id), undef, "unregistered object not retrieved";
        is scalar keys %$ob_reg, 0, "object registry empty";
        is register($obj), $obj, "object returned by register";
        is scalar keys %$ob_reg, 1, "object registry nonempty";
        is id_2obj($id), $obj, "registered object retrieved";

        # NEW
        is id_2obj($id),         undef, "unregistered object not \ 
retrieved";
        is scalar keys %$ob_reg, 0,     "object registry empty";
        is register($obj),       $obj,  "object returned by register";
        is scalar keys %$ob_reg, 1,     "object registry nonempty";
        is id_2obj($id),         $obj,  "registered object retrieved";

      This will cause some changes in alignment, hopefully for the better,
      particularly in test code which often uses numerous parenless function
      calls with functions like 'ok', 'is', 'is_deeply', ....

    - Two new parameters were added to control the block types to which the
      -bl (--opening-brace-on-new-line) flag applies.  The new parameters are
      -block-left-list=s, or -bll=s, and --block-left-exclusion-list=s,
      or -blxl=s.  Previously the -bl flag was 'hardwired' to apply to
      nearly all blocks. The default values of the new parameters
      retain the the old default behavior but allow it to be changed.

    - The default behavior of the -bli (-brace-left-and-indent) flag has changed
      slightly.  Previously, if you set -bli, then the -bl flag would also
      automatically be set.  Consequently, block types which were not included
      in the default list for -bli would get -bl formatting.  This is no longer done,
      and these two styles are now controlled independently.  The manual describes
      the controls.  If you want to recover the exact previous default behavior of
      the -bli then add the -bl flag.

    - A partial fix was made for issue for git #74. The -lp formatting style was
      being lost when a one-line anonymous sub was followed by a closing brace.

    - Fixed issue git #73, in which the -nfpva flag was not working correctly.
      Some unwanted vertical alignments of spaced function perens
      were being made.

    - Updated the man pages to clarify the flags -valign and -novalign
      for turning vertical alignment on and off (issue git #72).
      Added parameters -vc -vsc -vbc for separately turning off vertical
      alignment of code, side comments and block comments.

    - Fixed issue git #68, where a blank line following a closing code-skipping
      comment, '#>>V', could be lost.

    - This version runs 10 to 15 percent faster on large files than the
      previous release due to optimizations made with the help of NYTProf.

    - This version of perltidy was stress-tested for many cpu hours with
      random input parameters. No instabilities,  internal fault checks,
      undefined variable references or other irregularities were seen.

    - Numerous minor fixes have been made, mostly very rare formatting instabilities
      found in random testing. An effort has been made to minimize changes to
      existing formatting that these fixes produce, but occasional changes
      may occur. Many of these updates are listed at:

           https://github.com/perltidy/perltidy/blob/master/local-docs/BugLog.pod
   2021-10-26 12:20:11 by Nia Alarie | Files touched by this commit (3016)
Log message:
archivers: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Could not be committed due to merge conflict:
devel/py-traitlets/distinfo

The following distfiles were unfetchable (note: some may be only fetched
conditionally):

./devel/pvs/distinfo pvs-3.2-solaris.tgz
./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip
   2021-10-07 15:44:44 by Nia Alarie | Files touched by this commit (3017)
Log message:
devel: Remove SHA1 hashes for distfiles
   2021-05-24 21:56:06 by Thomas Klausner | Files touched by this commit (3575)
Log message:
*: recursive bump for perl 5.34
   2020-09-13 09:54:02 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
p5-Perl-Tidy: update to 20200907.

## 2020 09 07

    - Fixed bug git #37, an error when the combination -scbb -csc was used.
      It occurs in perltidy versions 20200110, 20200619, and 20200822.  What \ 
happens is
      that when two consecutive lines with isolated closing braces had new side
      comments generated by the -csc parameter, a separating newline was missing.
      The resulting script will not then run, but worse, if it is reformatted with
      the same parameters then closing side comments could be overwritten and data
      lost.

      This problem was found during automated random testing.  The parameter
      -scbb is rarely used, which is probably why this has not been reported.  Please
      upgrade your version.

    - Added parameter --non-indenting-braces, or -nib, which prevents
      code from indenting one level if it follows an opening brace marked
      with a special side comment, '#<<<'.  For example,

                    { #<<<   a closure to contain lexical vars

                    my $var;  # this line does not indent

                    }

                    # this line cannot 'see' $var;

      This is on by default.  If your code happens to have some
      opening braces followed by '#<<<', and you
      don't want this, you can use -nnib to deactivate it.

    - Side comment locations reset at a line ending in a level 0 open
      block, such as when a new multi-line sub begins.  This is intended to
      help keep side comments from drifting to far to the right.

Next | Query returned 56 messages, browsing 1 to 10 | Previous