+<h2>2020 01 10</h2>
+
+<pre><code>- This release adds a flag to control the feature RT#130394 (allow short nested blocks)
+ 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:
+
+ -olbn=0 break nested one-line blocks into multiple lines [new DEFAULT]
+ -olbn=1 stable; keep existing nested-one line blocks intact [previous DEFAULT]
+
+ For example, consider this input line:
+
+ foreach (@list) { if ($_ eq $asked_for) { last } ++$found }
+
+ The new default behavior (-olbn=0), and behavior prior to version 20191203, is to break it into multiple lines:
+
+ foreach (@list) {
+ if ( $_ eq $asked_for ) { last }
+ ++$found;
+ }
+
+ To keep nested one-line blocks such as this on a single line you can add the parameter -olbn=1.
+
+- 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
+ 'cpanm Perl::Tidy'
+</code></pre>
+
+<h2>2019 12 03</h2>
+
+<pre><code>- Fixed issue RT#131115: -bli option not working correctly.
+ Closing braces were not indented in some cases due to a glitch
+ introduced in version 20181120.
+
+- Fixed issue RT#130394: Allow short nested blocks. Given the following
+
+ $factorial = sub { reduce { $a * $b } 1 .. 11 };
+
+ Previous versions would always break the sub block because it
+ contains another block (the reduce block). The fix keeps
+ short one-line blocks such as this intact.
+
+- Implement issue RT#130640: Allow different subroutine keywords.
+ Added a flag --sub-alias-list=s or -sal=s, where s is a string with
+ one or more aliases for 'sub', separated by spaces or commas.
+ For example,
+
+ 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
+ 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
+
+ sub usage();
+
+ The result will be:
+ sub usage(); # i=0 [no space]
+ sub usage(); # i=1 [default; follows input]
+ sub usage (); # i=2 [space]
+
+- Fixed issue git#16, minor vertical alignment issue.
+
+- Fixed issue git#10, minor conflict of -wn and -ce
+
+- Improved some vertical alignments involving two lines.
+</code></pre>
+
+<h2>2019 09 15</h2>
+
+<pre><code>- 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
+ is '<source_stream>'.
+
+- implement issue RT#130425: check mode. A new flag '--assert-tidy'
+ will cause an error message if the output script is not identical to
+ the input script. For completeness, the opposite flag '--assert-untidy'
+ has also been added. The next item, RT#130297, insures that the script
+ will exit with a non-zero exit flag if the assertion fails.
+
+- fixed issue RT#130297; the perltidy script now exits with a nonzero exit
+ status if it wrote to the standard error output. Prevously only fatal
+ run errors produced a non-zero exit flag. Now, even non-fatal messages
+ requested with the -w flag will cause a non-zero exit flag. The exit
+ flag now has these values:
+
+ 0 = no errors
+ 1 = perltidy could not run to completion due to errors
+ 2 = perltidy ran to completion with error messages
+
+- added warning message for RT#130008, which warns of conflicting input
+ parameters -iob and -bom or -boc.
+
+- fixed RT#129850; concerning a space between a closing block brace and
+ opening bracket or brace, as occurs before the '[' in this line:
+
+ my @addunix = map { File::Spec::Unix->catfile( @ROOT, @$_ ) } ['b'];
+
+ Formerly, any space was removed. Now it is optional, and the output will
+ follow the input.
+
+- fixed issue git#13, needless trailing whitespace in error message
+
+- fixed issue git#9: if the -ce (--cuddled-else) flag is used,
+ do not try to form new one line blocks for a block type
+ specified with -cbl, particularly map, sort, grep
+
+- iteration speedup for unchanged code. Previously, when iterations were
+ requested, at least two formatting passes were made. Now just a single pass
+ is made if the formatted code is identical to the input code.
+
+- some improved vertical alignments
+</code></pre>
+