From 650caf193158154d217194f2953601b54b0ec4ae Mon Sep 17 00:00:00 2001 From: Steve Hancock Date: Wed, 31 Jan 2024 08:49:18 -0800 Subject: [PATCH] update to v20240202 --- CHANGES.md | 23 ++--- bin/perltidy | 2 +- docs/ChangeLog.html | 104 +++++++++++++-------- docs/Tidy.html | 2 +- docs/perltidy.html | 17 +++- docs/stylekey.html | 2 +- lib/Perl/Tidy.pm | 2 +- lib/Perl/Tidy.pod | 2 +- lib/Perl/Tidy/Debugger.pm | 2 +- lib/Perl/Tidy/Diagnostics.pm | 2 +- lib/Perl/Tidy/FileWriter.pm | 2 +- lib/Perl/Tidy/Formatter.pm | 2 +- lib/Perl/Tidy/HtmlWriter.pm | 2 +- lib/Perl/Tidy/IOScalar.pm | 2 +- lib/Perl/Tidy/IOScalarArray.pm | 2 +- lib/Perl/Tidy/IndentationItem.pm | 2 +- lib/Perl/Tidy/Logger.pm | 2 +- lib/Perl/Tidy/Tokenizer.pm | 2 +- lib/Perl/Tidy/VerticalAligner.pm | 2 +- lib/Perl/Tidy/VerticalAligner/Alignment.pm | 2 +- lib/Perl/Tidy/VerticalAligner/Line.pm | 9 +- 21 files changed, 115 insertions(+), 72 deletions(-) diff --git a/CHANGES.md b/CHANGES.md index ab049c3a..daa238f2 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -1,6 +1,6 @@ # Perltidy Change Log -## 2023 09 12.13 +## 2024 02 02 - Added --valign-signed-numbers, or -vsn. This improves the appearance of columns of numbers by aligning leading algebraic signs. For example: @@ -61,7 +61,6 @@ produces a file with lines which look something like - ... 1778:u: my $input_file 6089:r: my $j: reused - see line 6076 @@ -73,14 +72,13 @@ note - an optional note referring to another line The issue is indicated by a letter which may be one of: + r: reused variable name s: sigil change but reused bareword p: lexical variable with scope in multiple packages u: unused variable - This is very useful for locating problem areas and even bugs in code. - As an example, after it was developed it was applied to the perltidy - source code and it revealed two bugs; fortunately both were benign. + This is very useful for locating problem areas and bugs in code. - Added a related flag --warn-variable-types=string (-wvt=string) option to warn if certain types of variables are found in a script. The types @@ -97,12 +95,11 @@ The manual has further details. - All parameters taking integer values are now checked for - out-of-range values before processing starts. When a - minimum or maximum range is exceeded, the new default - behavior is to write a warning message, reset the - value to its default setting, and continue. If this default - behavior causes a problem, it can be changed with the new - parameter B<--integer-range-check=n>, or B<-irc=n>, as follows: + out-of-range values before processing starts. When a maximum or + maximum range is exceeded, the new default behavior is to write a + warning message, reset the value to its default setting, and continue. + This default behavior can be changed with the new parameter + --integer-range-check=n, or -irc=n, as follows: n=0 skip check completely (for stress-testing perltidy only) n=1 reset bad values to defaults but do not issue a warning @@ -169,8 +166,8 @@ - The -DEBUG option no longer automatically also writes a .LOG file. Use --show-options if the .LOG file is needed. - - The run time of this version with all new options in use is no - greater than the previous version thanks to optimization work. + - The run time of this version with all new options in use is no greater + than that of the previous version thanks to optimization work. ## 2023 09 12 diff --git a/bin/perltidy b/bin/perltidy index 26b12f68..9cc4b9dd 100755 --- a/bin/perltidy +++ b/bin/perltidy @@ -6265,7 +6265,7 @@ The perltidy binary uses the Perl::Tidy module and is installed when that module =head1 VERSION -This man page documents perltidy version 20230912.13 +This man page documents perltidy version 20240202 =head1 BUG REPORTS diff --git a/docs/ChangeLog.html b/docs/ChangeLog.html index 9a10efb8..4cbb3c0b 100644 --- a/docs/ChangeLog.html +++ b/docs/ChangeLog.html @@ -1,6 +1,6 @@

Perltidy Change Log

-

2023 09 12.13

+

2024 02 02

- Added --valign-signed-numbers, or -vsn. This improves the appearance
   of columns of numbers by aligning leading algebraic signs.  For example:
@@ -34,6 +34,7 @@
 
 - Added --dump-mixed-call-parens (-dmcp ) which will dump a list of
   operators which are sometimes followed by parens and sometimes not.
+  This can be useful for developing a uniform style for selected operators.
   Issue git #128. For example
 
      perltidy -dmcp somefile.pl >out.txt
@@ -54,13 +55,12 @@
   will format as normal but warn if any user subs are called without parens.
 
 - Added --dump-unusual-variables (-duv) option to dump a list of
-  variables with certain properties of interest. For example
+  variables with certain properties of interest.  For example
 
      perltidy -duv somefile.pl >vars.txt
 
   produces a file with lines which look something like
 
-     ...
      1778:u: my $input_file
      6089:r: my $j: reused - see line 6076
 
@@ -72,11 +72,14 @@
     note          - an optional note referring to another line
 
   The issue is indicated by a letter which may be one of:
+
     r: reused variable name
     s: sigil change but reused bareword
     p: lexical variable with scope in multiple packages
     u: unused variable
 
+  This is very useful for locating problem areas and bugs in code.
+
 - Added a related flag --warn-variable-types=string (-wvt=string) option
   to warn if certain types of variables are found in a script. The types
   are a space-separated string which may include 'r', 's', and 'p' but
@@ -92,12 +95,11 @@
   The manual has further details.
 
 - All parameters taking integer values are now checked for
-  out-of-range values before processing starts. When a
-  minimum or maximum range is exceeded, the new default
-  behavior is to write a warning message, reset the
-  value to its default setting, and continue.  If this default
-  behavior causes a problem, it can be changed with the new
-  parameter B<--integer-range-check=n>, or B<-irc=n>, as follows:
+  out-of-range values before processing starts. When a maximum or
+  maximum range is exceeded, the new default behavior is to write a
+  warning message, reset the value to its default setting, and continue.
+  This default behavior can be changed with the new parameter
+  --integer-range-check=n, or -irc=n, as follows:
 
     n=0  skip check completely (for stress-testing perltidy only)
     n=1  reset bad values to defaults but do not issue a warning
@@ -140,8 +142,32 @@
   emit an else block when two elsif blocks were separated by a hanging
   side comment (a very rare situation).
 
+- When braces are detected to be unbalanced, an attempt is made to
+  localize the error by comparing the indentation at closing braces
+  with their actual nesting levels. This can be useful for files which
+  have previously been formatted by perltidy. To illustrate, a test was
+  made in which the closing brace at line 30644 was commented out in
+  a file with a total of over 62000 lines.  The new error message is
+
+    Final nesting depth of '{'s is 1
+    The most recent un-matched '{' is on line 6858
+    ...
+    Table of nesting level differences at closing braces.
+    This might help localize brace errors if the file was previously formatted.
+    line:  (brace level) - (level expected from old indentation)
+    30643: 0
+    30645: 1
+
+  Previously, the error file only indicated that the error in this case
+  was somewhere after line 6858, so the new table is very helpful. Closing
+  brace indentation is checked because it is unambiguous and can be done
+  very efficiently.
+
 - The -DEBUG option no longer automatically also writes a .LOG file.
   Use --show-options if the .LOG file is needed.
+
+- The run time of this version with all new options in use is no greater
+  than that of the previous version thanks to optimization work.
 

2023 09 12

@@ -1168,7 +1194,7 @@ signatures. Reformatting with the current version will fix the problem.
- Added support for Switch::Plain syntax, issue git #31.
 
-- Fixed minor problem where trailing 'unless' clauses were not 
+- Fixed minor problem where trailing 'unless' clauses were not
   getting vertically aligned.
 
 - Added a parameter --logical-padding or -lop to allow logical padding
@@ -1186,35 +1212,35 @@ signatures.  Reformatting with the current version will fix the problem.
   'teefile' call parameters.  These output streams are rarely used but
   they are now treated the same as any 'logfile' stream.
 
-- add option --break-at-old-semicolon-breakpoints', -bos, requested 
+- add option --break-at-old-semicolon-breakpoints', -bos, requested
   in RT#131644.  This flag will keep lines beginning with a semicolon.
 
 - Added --use-unicode-gcstring to control use of Unicode::GCString for
-  evaluating character widths of encoded data.  The default is 
+  evaluating character widths of encoded data.  The default is
   not to use this (--nouse-unicode-gcstring). If this flag is set,
-  perltidy will look for Unicode::GCString and, if found, will use it 
+  perltidy will look for Unicode::GCString and, if found, will use it
   to evaluate character display widths.  This can improve displayed
   vertical alignment for files with wide characters.  It is a nice
   feature but it is off by default to avoid conflicting formatting
-  when there are multiple developers.  Perltidy installation does not 
-  require Unicode::GCString, so users wanting to use this feature need 
+  when there are multiple developers.  Perltidy installation does not
+  require Unicode::GCString, so users wanting to use this feature need
   set this flag and also to install Unicode::GCString separately.
 
 - Added --character-encoding=guess or -guess to have perltidy guess
-  if a file (or other input stream) is encoded as -utf8 or some 
-  other single-byte encoding. This is useful when processing a mixture 
+  if a file (or other input stream) is encoded as -utf8 or some
+  other single-byte encoding. This is useful when processing a mixture
   of file types, such as utf8 and latin-1.
 
   Please Note: The default encoding has been set to be 'guess'
-  instead of 'none'. This seems like the best default, since 
+  instead of 'none'. This seems like the best default, since
   it allows perltidy work properly with both
   utf8 files and older latin-1 files.  The guess mode uses Encode::Guess,
-  which is included in standard perl distributions, and only tries to 
-  guess if a file is utf8 or not, never any other encoding.  If the guess is 
-  utf8, and if the file successfully decodes as utf8, then it the encoding 
-  is assumed to be utf8.  Otherwise, no encoding is assumed. 
-  If you do not want to use this new default guess mode, or have a 
-  problem with it, you can set --character-encoding=none (the previous 
+  which is included in standard perl distributions, and only tries to
+  guess if a file is utf8 or not, never any other encoding.  If the guess is
+  utf8, and if the file successfully decodes as utf8, then it the encoding
+  is assumed to be utf8.  Otherwise, no encoding is assumed.
+  If you do not want to use this new default guess mode, or have a
+  problem with it, you can set --character-encoding=none (the previous
   default) or --character-encoding=utf8 (if you deal with utf8 files).
 
 - Specific encodings of input files other than utf8 may now be given, for
@@ -1236,11 +1262,11 @@ signatures.  Reformatting with the current version will fix the problem.
 

2020 01 10

- This release adds a flag to control the feature RT#130394 (allow short nested blocks)
-  introduced in the previous release.  Unfortunately that feature breaks 
+  introduced in the previous release.  Unfortunately that feature breaks
   RPerl installations, so a control flag has been introduced and that feature is now
   off by default.  The flag is:
 
-  --one-line-block-nesting=n, or -olbn=n, where n is an integer as follows: 
+  --one-line-block-nesting=n, or -olbn=n, where n is an integer as follows:
 
   -olbn=0 break nested one-line blocks into multiple lines [new DEFAULT]
   -olbn=1 stable; keep existing nested-one line blocks intact [previous DEFAULT]
@@ -1261,8 +1287,8 @@ signatures.  Reformatting with the current version will fix the problem.
 - Fixed issue RT#131288: parse error for un-prototyped constant function without parenthesized
   call parameters followed by ternary.
 
-- Fixed issue RT#131360, installation documentation.  Added a note that the binary 
-  'perltidy' comes with the Perl::Tidy module. They can both normally be installed with 
+- Fixed issue RT#131360, installation documentation.  Added a note that the binary
+  'perltidy' comes with the Perl::Tidy module. They can both normally be installed with
   'cpanm Perl::Tidy'
 
@@ -1285,19 +1311,19 @@ signatures. Reformatting with the current version will fix the problem. one or more aliases for 'sub', separated by spaces or commas. For example, - perltidy -sal='method fun' + perltidy -sal='method fun' will cause the perltidy to treat the words 'method' and 'fun' to be treated the same as if they were 'sub'. -- Added flag --space-prototype-paren=i, or -spp=i, to control spacing +- Added flag --space-prototype-paren=i, or -spp=i, to control spacing before the opening paren of a prototype, where i=0, 1, or 2: i=0 no space i=1 follow input [current and default] i=2 always space Previously, perltidy always followed the input. - For example, given the following input + For example, given the following input sub usage(); @@ -1315,16 +1341,16 @@ signatures. Reformatting with the current version will fix the problem.

2019 09 15

-
- fixed issue RT#130344: false warning "operator in print statement" 
-  for "use lib". 
+
- fixed issue RT#130344: false warning "operator in print statement"
+  for "use lib".
 
 - fixed issue RT#130304: standard error output should include filename.
-  When perltidy error messages are directed to the standard error output 
-  with -se or --standard-error-output, the message lines now have a prefix 
-  'filename:' for clarification in case multiple files 
-  are processed, where 'filename' is the name of the input file.  If 
-  input is from the standard input the displayed filename is '<stdin>', 
-  and if it is from a data structure then displayed filename 
+  When perltidy error messages are directed to the standard error output
+  with -se or --standard-error-output, the message lines now have a prefix
+  'filename:' for clarification in case multiple files
+  are processed, where 'filename' is the name of the input file.  If
+  input is from the standard input the displayed filename is '<stdin>',
+  and if it is from a data structure then displayed filename
   is '<source_stream>'.
 
 - implement issue RT#130425: check mode.  A new flag '--assert-tidy'
diff --git a/docs/Tidy.html b/docs/Tidy.html
index 3ed220f8..86b73c94 100644
--- a/docs/Tidy.html
+++ b/docs/Tidy.html
@@ -399,7 +399,7 @@
 
 

VERSION

-

This man page documents Perl::Tidy version 20230912.13

+

This man page documents Perl::Tidy version 20240202

LICENSE

diff --git a/docs/perltidy.html b/docs/perltidy.html index 7cdcc71a..310d993c 100644 --- a/docs/perltidy.html +++ b/docs/perltidy.html @@ -4009,7 +4009,20 @@

In a future release -vsn will become the default.

-

This option has a control parameter --valign-signed-number-limit=N, or -vsnl=N. This value controls formatting of very long columns of numbers and should not normally need to be changed. To see the function of this parameter, consider a very long column of just unsigned numbers, say 1000 lines. If we add a single negative number, it is undesirable to move all of the other lines over by one space. This would create many lines of file differences but not really improve the appearance when a local section of the table was viewed. The number N avoids this problem by not adding extra indentation to a run of more than N lines of unsigned numbers. The default value, N=20, is set to be approximately the number of lines for which a viewer does not normally see both ends of a long column of unsigned numbers on a single page.

+

Some points regarding -vsn are:

+ +
    + +
  • This option works by inserting a single space ahead of unsigned numbers when possible. This is not done if it would require increasing the maximum width of a column.

    + +
  • +
  • This option is mainly limited to lists of comma-separated numbers. For multiline lists of numbers, having trailing commas can sometimes improve the results. If missing, perltidy can add them for example with parameters -wtc=b -atc. See "Adding and Deleting Commas".

    + +
  • +
  • This option has a control parameter --valign-signed-number-limit=N, or -vsnl=N. This value controls formatting of very long columns of numbers and should not normally need to be changed. To see its purpose, consider a very long column of just unsigned numbers, say 1000 lines. If we add a single negative number, it is undesirable to move all of the other numbers over by one space. This would create many lines of file differences but not really improve the appearance when a local section of the table was viewed. The number N avoids this problem by not adding extra indentation to a run of more than N lines of unsigned numbers. The default value, N=20, is set to be a number of lines for which the ends of a long column of unsigned numbers are not normally both in view.

    + +
  • +
@@ -4871,7 +4884,7 @@

VERSION

-

This man page documents perltidy version 20230912.13

+

This man page documents perltidy version 20240202

BUG REPORTS

diff --git a/docs/stylekey.html b/docs/stylekey.html index e70b5a65..d5d14725 100644 --- a/docs/stylekey.html +++ b/docs/stylekey.html @@ -390,7 +390,7 @@

The -vt=2 style does not limit itself to a single indentation step per line.

-

Note that in the above example the function 'do_sumething_about_it' started on a new line. This is because it follows an opening code block brace and is governed by the flag previously set in "Block Brace Vertical Tightness".

+

Note that in the above example the function 'do_something_about_it' started on a new line. This is because it follows an opening code block brace and is governed by the flag previously set in "Block Brace Vertical Tightness".

Closing Token Placement

diff --git a/lib/Perl/Tidy.pm b/lib/Perl/Tidy.pm index 00798412..6ec7010b 100644 --- a/lib/Perl/Tidy.pm +++ b/lib/Perl/Tidy.pm @@ -131,7 +131,7 @@ BEGIN { # then the Release version must be bumped, and it is probably past time for # a release anyway. - $VERSION = '20230912.13'; + $VERSION = '20240202'; } ## end BEGIN sub DESTROY { diff --git a/lib/Perl/Tidy.pod b/lib/Perl/Tidy.pod index 47eb9efc..a8861dc0 100644 --- a/lib/Perl/Tidy.pod +++ b/lib/Perl/Tidy.pod @@ -469,7 +469,7 @@ The module 'Perl::Tidy' comes with a binary 'perltidy' which is installed when t =head1 VERSION -This man page documents Perl::Tidy version 20230912.13 +This man page documents Perl::Tidy version 20240202 =head1 LICENSE diff --git a/lib/Perl/Tidy/Debugger.pm b/lib/Perl/Tidy/Debugger.pm index d2219483..78614631 100644 --- a/lib/Perl/Tidy/Debugger.pm +++ b/lib/Perl/Tidy/Debugger.pm @@ -8,7 +8,7 @@ package Perl::Tidy::Debugger; use strict; use warnings; use English qw( -no_match_vars ); -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use constant EMPTY_STRING => q{}; use constant SPACE => q{ }; diff --git a/lib/Perl/Tidy/Diagnostics.pm b/lib/Perl/Tidy/Diagnostics.pm index 56cbb473..f1967824 100644 --- a/lib/Perl/Tidy/Diagnostics.pm +++ b/lib/Perl/Tidy/Diagnostics.pm @@ -18,7 +18,7 @@ package Perl::Tidy::Diagnostics; use strict; use warnings; use English qw( -no_match_vars ); -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use constant EMPTY_STRING => q{}; diff --git a/lib/Perl/Tidy/FileWriter.pm b/lib/Perl/Tidy/FileWriter.pm index 12d1a1d8..40e28884 100644 --- a/lib/Perl/Tidy/FileWriter.pm +++ b/lib/Perl/Tidy/FileWriter.pm @@ -16,7 +16,7 @@ package Perl::Tidy::FileWriter; use strict; use warnings; -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use constant DEVEL_MODE => 0; use constant EMPTY_STRING => q{}; diff --git a/lib/Perl/Tidy/Formatter.pm b/lib/Perl/Tidy/Formatter.pm index 05585ff9..d6f9ba39 100644 --- a/lib/Perl/Tidy/Formatter.pm +++ b/lib/Perl/Tidy/Formatter.pm @@ -75,7 +75,7 @@ use constant SPACE => q{ }; use Carp; use English qw( -no_match_vars ); use List::Util qw( min max first ); # min, max first are in Perl 5.8 -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; # The Tokenizer will be loaded with the Formatter ##use Perl::Tidy::Tokenizer; # for is_keyword() diff --git a/lib/Perl/Tidy/HtmlWriter.pm b/lib/Perl/Tidy/HtmlWriter.pm index 1354c0b1..ad870308 100644 --- a/lib/Perl/Tidy/HtmlWriter.pm +++ b/lib/Perl/Tidy/HtmlWriter.pm @@ -7,7 +7,7 @@ package Perl::Tidy::HtmlWriter; use strict; use warnings; -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use Carp; use English qw( -no_match_vars ); diff --git a/lib/Perl/Tidy/IOScalar.pm b/lib/Perl/Tidy/IOScalar.pm index 64458ab4..92a6c386 100644 --- a/lib/Perl/Tidy/IOScalar.pm +++ b/lib/Perl/Tidy/IOScalar.pm @@ -10,7 +10,7 @@ package Perl::Tidy::IOScalar; use strict; use warnings; use Carp; -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use constant DEVEL_MODE => 0; use constant EMPTY_STRING => q{}; diff --git a/lib/Perl/Tidy/IOScalarArray.pm b/lib/Perl/Tidy/IOScalarArray.pm index 7a223fac..605161cf 100644 --- a/lib/Perl/Tidy/IOScalarArray.pm +++ b/lib/Perl/Tidy/IOScalarArray.pm @@ -14,7 +14,7 @@ package Perl::Tidy::IOScalarArray; use strict; use warnings; use Carp; -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use constant DEVEL_MODE => 0; diff --git a/lib/Perl/Tidy/IndentationItem.pm b/lib/Perl/Tidy/IndentationItem.pm index 7da98306..6a17661a 100644 --- a/lib/Perl/Tidy/IndentationItem.pm +++ b/lib/Perl/Tidy/IndentationItem.pm @@ -9,7 +9,7 @@ package Perl::Tidy::IndentationItem; use strict; use warnings; -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; BEGIN { diff --git a/lib/Perl/Tidy/Logger.pm b/lib/Perl/Tidy/Logger.pm index 956b1ab9..8131aae9 100644 --- a/lib/Perl/Tidy/Logger.pm +++ b/lib/Perl/Tidy/Logger.pm @@ -8,7 +8,7 @@ package Perl::Tidy::Logger; use strict; use warnings; -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use Carp; use English qw( -no_match_vars ); diff --git a/lib/Perl/Tidy/Tokenizer.pm b/lib/Perl/Tidy/Tokenizer.pm index 2153e7fc..18268659 100644 --- a/lib/Perl/Tidy/Tokenizer.pm +++ b/lib/Perl/Tidy/Tokenizer.pm @@ -33,7 +33,7 @@ use strict; use warnings; use English qw( -no_match_vars ); -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use Carp; diff --git a/lib/Perl/Tidy/VerticalAligner.pm b/lib/Perl/Tidy/VerticalAligner.pm index 2d183004..91b8c4ee 100644 --- a/lib/Perl/Tidy/VerticalAligner.pm +++ b/lib/Perl/Tidy/VerticalAligner.pm @@ -5,7 +5,7 @@ use Carp; { #<<< A non-indenting brace to contain all lexical variables -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use English qw( -no_match_vars ); use Perl::Tidy::VerticalAligner::Alignment; use Perl::Tidy::VerticalAligner::Line; diff --git a/lib/Perl/Tidy/VerticalAligner/Alignment.pm b/lib/Perl/Tidy/VerticalAligner/Alignment.pm index 81ce1e63..fe8c301f 100644 --- a/lib/Perl/Tidy/VerticalAligner/Alignment.pm +++ b/lib/Perl/Tidy/VerticalAligner/Alignment.pm @@ -9,7 +9,7 @@ package Perl::Tidy::VerticalAligner::Alignment; use strict; use warnings; -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; sub new { my ( $class, $rarg ) = @_; diff --git a/lib/Perl/Tidy/VerticalAligner/Line.pm b/lib/Perl/Tidy/VerticalAligner/Line.pm index f8621d09..75f4b37c 100644 --- a/lib/Perl/Tidy/VerticalAligner/Line.pm +++ b/lib/Perl/Tidy/VerticalAligner/Line.pm @@ -10,7 +10,7 @@ package Perl::Tidy::VerticalAligner::Line; use strict; use warnings; -our $VERSION = '20230912.13'; +our $VERSION = '20240202'; use English qw( -no_match_vars ); sub AUTOLOAD { @@ -34,6 +34,11 @@ EOM exit 1; } ## end sub AUTOLOAD +sub DESTROY { + + # required to avoid call to AUTOLOAD in some versions of perl +} + # Constructor may be called as a class method sub new { my ( $class, $ri ) = @_; @@ -66,6 +71,8 @@ sub current_field_width { sub increase_field_width { my ( $self, $j, $pad ) = @_; + + # Increase the width of alignment field $j by $pad spaces my $jmax = $self->{jmax}; foreach ( $j .. $jmax ) { my $alignment = $self->{ralignments}->[$_]; -- 2.39.5