From: Steve Hancock Date: Fri, 30 Oct 2020 01:42:12 +0000 (-0700) Subject: update BugLog X-Git-Tag: 20201001.03~23 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=edd1f4c8c02dd38bfbedcb82ed0080e5eb17e2d8;p=perltidy.git update BugLog --- diff --git a/local-docs/BugLog.pod b/local-docs/BugLog.pod index ff3f8dd0..a89d29ef 100644 --- a/local-docs/BugLog.pod +++ b/local-docs/BugLog.pod @@ -2,12 +2,13 @@ =over 4 -=item b +=item B The exit status was always 0 for --assert-tidy if the user had turned off error -messages with -quiet. This has been fixed. +messages with -quiet. This was fixed by gluesys/master in 'fix exit +status for assert-tidy/untidy options', 625d250. -=item b +=item B A parsing error was encountered in a test parsing the following extruded signature: @@ -37,7 +38,7 @@ The file parses correctly now, with formatted output return "first=$first, third=$third"; } -=item b +=item B Several instances of incorrect array indexing were found in testing and fixed. These each involved incorrectly indexing with index -1. They were found by @@ -45,7 +46,7 @@ placing undefs at the end of arrays. None of these was causing incorrect formatting. They were fixed 26 Oct 2020 in 'fixed several instances of incorrect array indexing', c60f694. -=item b +=item B In stress testing perltidy with the -extrude option, the following test snippet @@ -68,7 +69,7 @@ Rerunning gives This was fixed 26 Oct 2020 in 'prevent breaking package names with trailing dashes', 9234be4. -=item b +=item B In stress testing perltidy with the -extrude option, using the following test snippet @@ -129,7 +130,7 @@ line with its surrounding tokens. A rule was added to do this. The new This update was added 26 Oct 2020, 'prevent syntax error by breaking dashed barewords', e121cae. -=item b +=item B Files for which 'severe errors' are found have always been output verbatim rather than being formatted. The definition of 'severe error' has been @@ -138,27 +139,27 @@ brace errors, and more than 3 "unexpected token type" parsing errors. The goal is to avoid formatting a non-perl script or a perl script with severe errors. So for example the following snippet has a level error of 2 -{{{{ -}} + {{{{ + }} was previously output with default parameters as -{ - { - { - {} - } + { + { + { + {} + } along with an error message. But now it is just output verbatim as -{{{{ -}} + {{{{ + }} along with an error message. This update was added 25 Oct 2020, 'avoid formatting files with more types of severe errors', 2a86f51. -=item b +=item B A statement such as the following was generating an error message at the colon: @@ -169,7 +170,7 @@ and the line now parses without error. The 'state.t' test file for perl 5.31 now formats without error. This was added 18 Oct 2020 in "add 'state' as keyword", d73e15f. -=item b +=item B Simple signatures (those without commas) were being parsed with code originally written for prototypes. This prevented them from being formatted with the @@ -202,7 +203,7 @@ This update was added 18 Oct 2020, in 'format all signatures separately from prototypes', e6a10f3. The test file 'signatures.t' distributed with perl5.31 formats without error now. -=item b +=item B A problem with parsing variables of the form $# and $#array was found in testing and fixed. For most variables the leading sigil may be separated from @@ -218,7 +219,7 @@ and is equivalent to $ans=40; This was being misparsed and was fixed 17 Oct 2020, in 'fixed parsing error with spaces in $#' a079cdb. -=item b +=item B During testing the following error was found and fixed. Given the following input snippet: @@ -247,7 +248,7 @@ a signature with multiple parameters and short enough to be a one-line block, as in the last sub definition line. This was fixed 17 Oct 2020 in 'fix missing line break for hash of subs with signatures', 51428db. -=item b +=item B Problems with parsing prototypes and signatures were found during testing and fixed 17 Oct 2020 in 'fixed problem parsing multi-line signatures with @@ -268,7 +269,7 @@ error: ) #foo))) { $a.$b } -=item b +=item B The following line caused a tokenization error in which the two slashes were parsed as a pattern. @@ -280,7 +281,7 @@ whose prototype is not known to perltidy, it has to guess whether the slash starts a pattern or is a division. The guessing logic was rewritten and improved 14 Oct 2020 in 'rewrote logic to guess if divide or pattern', afebe2f. -=item b +=item B The flag B<-bos>, or B<--break-at-old-semicolon-breakpoints>, keeps breaks at old isolated semicolons. For example @@ -298,7 +299,7 @@ semicolons, such as 'do' and anonymous subs. This was fixed 12 Oct 2020 in } ; -=item b +=item B If a line break occurs after B then it will now be kept. Previously it was dropped. For example, this would be kept intact: @@ -361,7 +362,6 @@ corrected formatting, we would have =back - =head1 Issues fixed after release 20200907 This is a detailed log of changes since the release 20200907. All bugs were @@ -369,7 +369,6 @@ found with the help of automated random testing. =over - =item B In random testing, the -mangle option introduced a syntax error by deleting @@ -747,7 +746,7 @@ These are known issues which have not been fixed. =over 4 -=item b +=item B Basic parsing of lexical subs works but some aspects of lexical subs are not yet functional. One of these is that unlike regular subs, lexical subs can override names of builtin functions. @@ -782,7 +781,7 @@ make different assumptions in this case. Another issue is that perltidy does not yet remember the extent of the scope of a lexical sub. -=item b +=item B Consider the following snippet: @@ -804,7 +803,7 @@ The problem can be avoid if parens are used: ok ( open($stdin, "<&", $1), 'open ... "<&", $magical_fileno') || _diag $!; -=item b +=item B Perltidy currently flags as an error a closing paren followed by an opening paren, as in the following @@ -812,3 +811,5 @@ paren, as in the following $subsubs[0]()(0) This syntax is ok. The example is from test 'current_sub.t' in perl5.31. + +=back