## 2022 06 01
- - The flag --encode-output-strings, or -eos, is now set on by default, as
- noted in the discussion of issue git #92. This has no effect on the use
- of the 'perltidy' binary but could change the behavior of programs which
- use the Perl::Tidy module on files encoded in UTF-8. If any problems are
- noticed, an emergency fix can be made by reverting to the old default with
- the flag -neos. For complete details see:
+ - Please note the following two significant changes in this distribution:
- https://github.com/perltidy/perltidy/blob/master/docs/eos_flag.md
+ - The flag --encode-output-strings, or -eos, is now set 'on' by default.
+ This has no effect on the use of the 'perltidy' binary script, but could
+ change the behavior of some programs which use the Perl::Tidy module on
+ files encoded in UTF-8. If any problems are noticed, an emergency fix
+ can be made by reverting to the old default by setting -neos. For
+ an explanation of why this change needs to be made see:
- - Add vertical alignment for qw quotes in 'use' statements (see issue #git 93).
- This is on by default but can be turned off with -vxl='q':
+ https://github.com/perltidy/perltidy/issues/92
+
+ https://github.com/perltidy/perltidy/blob/master/docs/eos_flag.md
+
+ - Add vertical alignment for qw quotes and empty parens in 'use'
+ statements (see issue #git 93). This new alignment is 'on' by default
+ and will change formatting as shown below. If this is not wanted it can
+ be turned off with the parameter -vxl='q' (--valign-exclude-list='q').
# old default or -vxl='q'
use Getopt::Long qw(GetOptions);
- Previously, if a -dsc command was used to delete all side comments,
then any special control comments for non-indenting braces got deleted too.
Now, these control side comments are retained when -dsc is set unless
- a -nnib flag is also set to deactivate them.
+ a -nnib (--nonon-indenting-braces) flag is also set to deactivate them.
- This version runs 15 to 20 percent faster on large files than the
previous release due to optimizations made with the help of Devel::NYTProf.
random input parameters. No failures to converge, internal fault checks,
undefined variable references or other irregularities were seen.
- - Fixed and reactivated two failing installation tests (they were reading
- a local .perltidyrc file)
-
## 2022 02 17
<h2>2022 06 01</h2>
-<pre><code>- The flag --encode-output-strings, or -eos, is now set on by default, as
- noted in the discussion of issue git #92. This has no effect on the use
- of the 'perltidy' binary but could change the behavior of programs which
- use the Perl::Tidy module on files encoded in UTF-8. If any problems are
- noticed, an emergency fix can be made by reverting to the old default with
- the flag -neos. For complete details see:
+<pre><code>- Please note the following two significant changes in this distribution:
- https://github.com/perltidy/perltidy/blob/master/docs/eos_flag.md
+- The flag --encode-output-strings, or -eos, is now set 'on' by default.
+ This has no effect on the use of the 'perltidy' binary script, but could
+ change the behavior of some programs which use the Perl::Tidy module on
+ files encoded in UTF-8. If any problems are noticed, an emergency fix
+ can be made by reverting to the old default by setting -neos. For
+ an explanation of why this change needs to be made see:
-- Add vertical alignment for qw quotes in 'use' statements (see issue #git 93).
- This is on by default but can be turned off with -vxl='q':
+ https://github.com/perltidy/perltidy/issues/92
+
+ https://github.com/perltidy/perltidy/blob/master/docs/eos_flag.md
+
+- Add vertical alignment for qw quotes and empty parens in 'use'
+ statements (see issue #git 93). This new alignment is 'on' by default
+ and will change formatting as shown below. If this is not wanted it can
+ be turned off with the parameter -vxl='q' (--valign-exclude-list='q').
# old default or -vxl='q'
use Getopt::Long qw(GetOptions);
- Previously, if a -dsc command was used to delete all side comments,
then any special control comments for non-indenting braces got deleted too.
Now, these control side comments are retained when -dsc is set unless
- a -nnib flag is also set to deactivate them.
+ a -nnib (--nonon-indenting-braces) flag is also set to deactivate them.
- This version runs 15 to 20 percent faster on large files than the
previous release due to optimizations made with the help of Devel::NYTProf.
- This version of perltidy 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.
-
-- Fixed and reactivated two failing installation tests (they were reading
- a local .perltidyrc file)
</code></pre>
<h2>2022 02 17</h2>
<p>In the present example, we are only looking for tokens of type <b>i</b> (identifiers), so the for loop skips past all other types. When an identifier is found, its actual text is checked to see if it is one being sought. If so, the above write_line prints the token and its line number.</p>
-<p>The <b>formatter</b> feature is relatively new in perltidy, and further documentation needs to be written to complete its description. However, several example programs have been written and can be found in the <b>examples</b> section of the source distribution. Probably the best way to get started is to find one of the examples which most closely matches your application and start modifying it.</p>
+<p>The <b>examples</b> section of the source distribution has some examples of programs which use the <b>formatter</b> option.</p>
<p>For help with perltidy's peculiar way of breaking lines into tokens, you might run, from the command line,</p>
<pre><code> perltidy -D filename</code></pre>
-<p>where <i>filename</i> is a short script of interest. This will produce <i>filename.DEBUG</i> with interleaved lines of text and their token types. The <b>-D</b> flag has been in perltidy from the beginning for this purpose. If you want to see the code which creates this file, it is <code>write_debug_entry</code> in Tidy.pm.</p>
+<p>where <i>filename</i> is a short script of interest. This will produce <i>filename.DEBUG</i> with interleaved lines of text and their token types. The <b>-D</b> flag has been in perltidy from the beginning for this purpose. If you want to see the code which creates this file, it is <code>sub Perl::Tidy::Debugger::write_debug_entry</code></p>
<h1 id="EXPORT">EXPORT</h1>
<h1 id="BUG-REPORTS">BUG REPORTS</h1>
-<p>A list of current bugs and issues can be found at the CPAN site <a href="https://rt.cpan.org/Public/Dist/Display.html?Name=Perl-Tidy">https://rt.cpan.org/Public/Dist/Display.html?Name=Perl-Tidy</a></p>
-
-<p>To report a new bug or problem, use the link on this page.</p>
-
<p>The source code repository is at <a href="https://github.com/perltidy/perltidy">https://github.com/perltidy/perltidy</a>.</p>
+<p>To report a new bug or problem, use the "issues" link on this page.</p>
+
<h1 id="SEE-ALSO">SEE ALSO</h1>
<p>The perltidy(1) man page describes all of the features of perltidy. It can be found at http://perltidy.sourceforge.net.</p>
<h1 id="DESCRIPTION">DESCRIPTION</h1>
-<p>Perltidy reads a perl script and writes an indented, reformatted script.</p>
+<p>Perltidy reads a perl script and writes an indented, reformatted script. This document describes the parameters available for controlling this formatting.</p>
+
+<p>Perltidy is a commandline frontend to the module Perl::Tidy. For documentation describing how to call the Perl::Tidy module from other applications see the separate documentation for Perl::Tidy. It is the file Perl::Tidy.pod in the source distribution.</p>
<p>Many users will find enough information in <a href="#EXAMPLES">"EXAMPLES"</a> to get started. New users may benefit from the short tutorial which can be found at http://perltidy.sourceforge.net/tutorial.html</p>
<h1 id="BUG-REPORTS">BUG REPORTS</h1>
-<p>A list of current bugs and issues can be found at the CPAN site <a href="https://rt.cpan.org/Public/Dist/Display.html?Name=Perl-Tidy">https://rt.cpan.org/Public/Dist/Display.html?Name=Perl-Tidy</a></p>
-
-<p>To report a new bug or problem, use the link on this page.</p>
-
<p>The source code repository is at <a href="https://github.com/perltidy/perltidy">https://github.com/perltidy/perltidy</a>.</p>
+<p>To report a new bug or problem, use the "issues" link on this page.</p>
+
<h1 id="COPYRIGHT">COPYRIGHT</h1>
<p>Copyright (c) 2000-2022 by Steve Hancock</p>
projects / perltidy.git / commitdiff