Dashboard

Editing: perltidy.html

<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<body>

<ul id="index">
 <li><a href="#NAME">NAME</a></li>
 <li><a href="#SYNOPSIS">SYNOPSIS</a></li>
 <li><a href="#DESCRIPTION">DESCRIPTION</a></li>
 <li><a href="#EXAMPLES">EXAMPLES</a></li>
 <li><a href="#OPTIONS---OVERVIEW">OPTIONS - OVERVIEW</a>
 <ul>
 <li><a href="#I-O-control">I/O control</a></li>
 </ul>
 </li>
 <li><a href="#FORMATTING-OPTIONS">FORMATTING OPTIONS</a>
 <ul>
 <li><a href="#Basic-Options">Basic Options</a></li>
 <li><a href="#Code-Indentation-Control">Code Indentation Control</a></li>
 <li><a href="#Whitespace-Control">Whitespace Control</a></li>
 <li><a href="#Comment-Controls">Comment Controls</a></li>
 <li><a href="#Skipping-Selected-Sections-of-Code">Skipping Selected Sections of Code</a></li>
 <li><a href="#Line-Break-Control">Line Break Control</a></li>
 <li><a href="#Controlling-List-Formatting">Controlling List Formatting</a></li>
 <li><a href="#Retaining-or-Ignoring-Existing-Line-Breaks">Retaining or Ignoring Existing Line Breaks</a></li>
 <li><a href="#Blank-Line-Control">Blank Line Control</a></li>
 <li><a href="#Styles">Styles</a></li>
 <li><a href="#Controlling-Vertical-Alignment">Controlling Vertical Alignment</a></li>
 <li><a href="#Other-Controls">Other Controls</a></li>
 </ul>
 </li>
 <li><a href="#HTML-OPTIONS">HTML OPTIONS</a></li>
 <li><a href="#SOME-COMMON-INPUT-CONVENTIONS">SOME COMMON INPUT CONVENTIONS</a>
 <ul>
 <li><a href="#Specifying-Block-Types">Specifying Block Types</a></li>
 <li><a href="#Specifying-File-Extensions">Specifying File Extensions</a></li>
 </ul>
 </li>
 <li><a href="#SWITCHES-WHICH-MAY-BE-NEGATED">SWITCHES WHICH MAY BE NEGATED</a></li>
 <li><a href="#LIMITATIONS">LIMITATIONS</a></li>
 <li><a href="#FILES">FILES</a></li>
 <li><a href="#ERROR-HANDLING">ERROR HANDLING</a></li>
 <li><a href="#SEE-ALSO">SEE ALSO</a></li>
 <li><a href="#INSTALLATION">INSTALLATION</a></li>
 <li><a href="#VERSION">VERSION</a></li>
 <li><a href="#BUG-REPORTS">BUG REPORTS</a></li>
 <li><a href="#COPYRIGHT">COPYRIGHT</a></li>
 <li><a href="#LICENSE">LICENSE</a></li>
 <li><a href="#DISCLAIMER">DISCLAIMER</a></li>
</ul>

perltidy - a perl script indenter and reformatter

<h1 id="SYNOPSIS">SYNOPSIS</h1>

<pre><code> perltidy [ options ] file1 file2 file3 ...
 (output goes to file1.tdy, file2.tdy, file3.tdy, ...)
 perltidy [ options ] file1 -o outfile
 perltidy [ options ] file1 -st &gt;outfile
 perltidy [ options ] &lt;infile &gt;outfile</code></pre>

<h1 id="DESCRIPTION">DESCRIPTION</h1>

Perltidy reads a perl script and writes an indented, reformatted script.

Many users will find enough information in <a href="#EXAMPLES">&quot;EXAMPLES&quot;</a> to get started. New users may benefit from the short tutorial which can be found at http://perltidy.sourceforge.net/tutorial.html

A convenient aid to systematically defining a set of style parameters can be found at http://perltidy.sourceforge.net/stylekey.html

Perltidy can produce output on either of two modes, depending on the existence of an -html flag. Without this flag, the output is passed through a formatter. The default formatting tries to follow the recommendations in perlstyle(1), but it can be controlled in detail with numerous input parameters, which are described in <a href="#FORMATTING-OPTIONS">&quot;FORMATTING OPTIONS&quot;</a>.

When the -html flag is given, the output is passed through an HTML formatter which is described in <a href="#HTML-OPTIONS">&quot;HTML OPTIONS&quot;</a>.

<h1 id="EXAMPLES">EXAMPLES</h1>

<pre><code> perltidy somefile.pl</code></pre>

This will produce a file somefile.pl.tdy containing the script reformatted using the default options, which approximate the style suggested in perlstyle(1). The source file somefile.pl is unchanged.

<pre><code> perltidy *.pl</code></pre>

Execute perltidy on all .pl files in the current directory with the default options. The output will be in files with an appended .tdy extension. For any file with an error, there will be a file with extension .ERR.

<pre><code> perltidy -b file1.pl file2.pl</code></pre>

Modify file1.pl and file2.pl in place, and backup the originals to file1.pl.bak and file2.pl.bak. If file1.pl.bak and/or file2.pl.bak already exist, they will be overwritten.

<pre><code> perltidy -b -bext=&#39;/&#39; file1.pl file2.pl</code></pre>

Same as the previous example except that the backup files file1.pl.bak and file2.pl.bak will be deleted if there are no errors.

<pre><code> perltidy -gnu somefile.pl</code></pre>

Execute perltidy on file somefile.pl with a style which approximates the GNU Coding Standards for C programs. The output will be somefile.pl.tdy.

<pre><code> perltidy -i=3 somefile.pl</code></pre>

Execute perltidy on file somefile.pl, with 3 columns for each level of indentation (-i=3) instead of the default 4 columns. There will not be any tabs in the reformatted script, except for any which already exist in comments, pod documents, quotes, and here documents. Output will be somefile.pl.tdy.

<pre><code> perltidy -i=3 -et=8 somefile.pl</code></pre>

Same as the previous example, except that leading whitespace will be entabbed with one tab character per 8 spaces.

<pre><code> perltidy -ce -l=72 somefile.pl</code></pre>

Execute perltidy on file somefile.pl with all defaults except use &quot;cuddled elses&quot; (-ce) and a maximum line length of 72 columns (-l=72) instead of the default 80 columns.

<pre><code> perltidy -g somefile.pl</code></pre>

Execute perltidy on file somefile.pl and save a log file somefile.pl.LOG which shows the nesting of braces, parentheses, and square brackets at the start of every line.

<pre><code> perltidy -html somefile.pl</code></pre>

This will produce a file somefile.pl.html containing the script with html markup. The output file will contain an embedded style sheet in the &lt;HEAD&gt; section which may be edited to change the appearance.

<pre><code> perltidy -html -css=mystyle.css somefile.pl</code></pre>

This will produce a file somefile.pl.html containing the script with html markup. This output file will contain a link to a separate style sheet file mystyle.css. If the file mystyle.css does not exist, it will be created. If it exists, it will not be overwritten.

<pre><code> perltidy -html -pre somefile.pl</code></pre>

Write an html snippet with only the PRE section to somefile.pl.html. This is useful when code snippets are being formatted for inclusion in a larger web page. No style sheet will be written in this case.

<pre><code> perltidy -html -ss &gt;mystyle.css</code></pre>

Write a style sheet to mystyle.css and exit.

<pre><code> perltidy -html -frm mymodule.pm</code></pre>

Write html with a frame holding a table of contents and the source code. The output files will be mymodule.pm.html (the frame), mymodule.pm.toc.html (the table of contents), and mymodule.pm.src.html (the source code).

<h1 id="OPTIONS---OVERVIEW">OPTIONS - OVERVIEW</h1>

The entire command line is scanned for options, and they are processed before any files are processed. As a result, it does not matter whether flags are before or after any filenames. However, the relative order of parameters is important, with later parameters overriding the values of earlier parameters.

For each parameter, there is a long name and a short name. The short names are convenient for keyboard input, while the long names are self-documenting and therefore useful in scripts. It is customary to use two leading dashes for long names, but one may be used.

Most parameters which serve as on/off flags can be negated with a leading &quot;n&quot; (for the short name) or a leading &quot;no&quot; or &quot;no-&quot; (for the long name). For example, the flag to outdent long quotes is -olq or --outdent-long-quotes. The flag to skip this is -nolq or --nooutdent-long-quotes or --no-outdent-long-quotes.

Options may not be bundled together. In other words, options -q and -g may NOT be entered as -qg.

Option names may be terminated early as long as they are uniquely identified. For example, instead of --dump-token-types, it would be sufficient to enter --dump-tok, or even --dump-t, to uniquely identify this command.

<h2 id="I-O-control">I/O control</h2>

The following parameters concern the files which are read and written.

<dl>

Show summary of usage and exit.

</dd>
<dt id="o-filename---outfile-filename">-o=filename, --outfile=filename</dt>
<dd>

Name of the output file (only if a single input file is being processed). If no output file is specified, and output is not redirected to the standard output (see -st), the output will go to filename.tdy. [Note: - does not redirect to standard output. Use -st instead.]

</dd>
<dt id="st---standard-output">-st, --standard-output</dt>
<dd>

Perltidy must be able to operate on an arbitrarily large number of files in a single run, with each output being directed to a different output file. Obviously this would conflict with outputting to the single standard output device, so a special flag, -st, is required to request outputting to the standard output. For example,

<pre><code> perltidy somefile.pl -st &gt;somefile.new.pl</code></pre>

This option may only be used if there is just a single input file. The default is -nst or --nostandard-output.

</dd>
<dt id="se---standard-error-output">-se, --standard-error-output</dt>
<dd>

If perltidy detects an error when processing file somefile.pl, its default behavior is to write error messages to file somefile.pl.ERR. Use -se to cause all error messages to be sent to the standard error output stream instead. This directive may be negated with -nse. Thus, you may place -se in a .perltidyrc and override it when desired with -nse on the command line.

</dd>
<dt id="oext-ext---output-file-extension-ext">-oext=ext, --output-file-extension=ext</dt>
<dd>

Change the extension of the output file to be ext instead of the default tdy (or html in case the --html option is used). See <a href="#Specifying-File-Extensions">&quot;Specifying File Extensions&quot;</a>.

</dd>
<dt id="opath-path---output-path-path">-opath=path, --output-path=path</dt>
<dd>

When perltidy creates a filename for an output file, by default it merely appends an extension to the path and basename of the input file. This parameter causes the path to be changed to path instead.

The path should end in a valid path separator character, but perltidy will try to add one if it is missing.

For example

<pre><code> perltidy somefile.pl -opath=/tmp/</code></pre>

will produce /tmp/somefile.pl.tdy. Otherwise, somefile.pl.tdy will appear in whatever directory contains somefile.pl.

If the path contains spaces, it should be placed in quotes.

This parameter will be ignored if output is being directed to standard output, or if it is being specified explicitly with the -o=s parameter.

</dd>
<dt id="b---backup-and-modify-in-place">-b, --backup-and-modify-in-place</dt>
<dd>

Modify the input file or files in-place and save the original with the extension .bak. Any existing .bak file will be deleted. See next item for changing the default backup extension, and for eliminating the backup file altogether.

A -b flag will be ignored if input is from standard input or goes to standard output, or if the -html flag is set.

In particular, if you want to use both the -b flag and the -pbp (--perl-best-practices) flag, then you must put a -nst flag after the -pbp flag because it contains a -st flag as one of its components, which means that output will go to the standard output stream.

</dd>
<dt id="bext-ext---backup-file-extension-ext">-bext=ext, --backup-file-extension=ext</dt>
<dd>

This parameter serves two purposes: (1) to change the extension of the backup file to be something other than the default .bak, and (2) to indicate that no backup file should be saved.

To change the default extension to something other than .bak see <a href="#Specifying-File-Extensions">&quot;Specifying File Extensions&quot;</a>.

A backup file of the source is always written, but you can request that it be deleted at the end of processing if there were no errors. This is risky unless the source code is being maintained with a source code control system.

To indicate that the backup should be deleted include one forward slash, /, in the extension. If any text remains after the slash is removed it will be used to define the backup file extension (which is always created and only deleted if there were no errors).

Here are some examples:

<pre><code> Parameter Extension Backup File Treatment
 &lt;-bext=bak&gt; F&lt;.bak&gt; Keep (same as the default behavior)
 &lt;-bext=&#39;/&#39;&gt; F&lt;.bak&gt; Delete if no errors
 &lt;-bext=&#39;/backup&#39;&gt; F&lt;.backup&gt; Delete if no errors
 &lt;-bext=&#39;original/&#39;&gt; F&lt;.original&gt; Delete if no errors</code></pre>

</dd>
<dt id="w---warning-output">-w, --warning-output</dt>
<dd>

Setting -w causes any non-critical warning messages to be reported as errors. These include messages about possible pod problems, possibly bad starting indentation level, and cautions about indirect object usage. The default, -nw or --nowarning-output, is not to include these warnings.

</dd>
<dt id="q---quiet">-q, --quiet</dt>
<dd>

Deactivate error messages (for running under an editor).

For example, if you use a vi-style editor, such as vim, you may execute perltidy as a filter from within the editor using something like

<pre><code> :n1,n2!perltidy -q</code></pre>

where <code>n1,n2</code> represents the selected text. Without the -q flag, any error message may mess up your screen, so be prepared to use your &quot;undo&quot; key.

</dd>
<dt id="log---logfile">-log, --logfile</dt>
<dd>

Save the .LOG file, which has many useful diagnostics. Perltidy always creates a .LOG file, but by default it is deleted unless a program bug is suspected. Setting the -log flag forces the log file to be saved.

</dd>
<dt id="g-n---logfile-gap-n">-g=n, --logfile-gap=n</dt>
<dd>

Set maximum interval between input code lines in the logfile. This purpose of this flag is to assist in debugging nesting errors. The value of <code>n</code> is optional. If you set the flag -g without the value of <code>n</code>, it will be taken to be 1, meaning that every line will be written to the log file. This can be helpful if you are looking for a brace, paren, or bracket nesting error.

Setting -g also causes the logfile to be saved, so it is not necessary to also include -log.

If no -g flag is given, a value of 50 will be used, meaning that at least every 50th line will be recorded in the logfile. This helps prevent excessively long log files.

Setting a negative value of <code>n</code> is the same as not setting -g at all.

</dd>
<dt id="npro---noprofile">-npro --noprofile</dt>
<dd>

Ignore any .perltidyrc command file. Normally, perltidy looks first in your current directory for a .perltidyrc file of parameters. (The format is described below). If it finds one, it applies those options to the initial default values, and then it applies any that have been defined on the command line. If no .perltidyrc file is found, it looks for one in your home directory.

If you set the -npro flag, perltidy will not look for this file.

</dd>
<dt id="pro-filename-or---profile-filename">-pro=filename or --profile=filename</dt>
<dd>

To simplify testing and switching .perltidyrc files, this command may be used to specify a configuration file which will override the default name of .perltidyrc. There must not be a space on either side of the &#39;=&#39; sign. For example, the line

<pre><code> perltidy -pro=testcfg</code></pre>

would cause file testcfg to be used instead of the default .perltidyrc.

A pathname begins with three dots, e.g. &quot;.../.perltidyrc&quot;, indicates that the file should be searched for starting in the current directory and working upwards. This makes it easier to have multiple projects each with their own .perltidyrc in their root directories.

</dd>
<dt id="opt---show-options">-opt, --show-options</dt>
<dd>

Write a list of all options used to the .LOG file. Please see --dump-options for a simpler way to do this.

</dd>
<dt id="f---force-read-binary">-f, --force-read-binary</dt>
<dd>

Force perltidy to process binary files. To avoid producing excessive error messages, perltidy skips files identified by the system as non-text. However, valid perl scripts containing binary data may sometimes be identified as non-text, and this flag forces perltidy to process them.

</dd>
<dt id="ast---assert-tidy">-ast, --assert-tidy</dt>
<dd>

This flag asserts that the input and output code streams are identical, or in other words that the input code is already &#39;tidy&#39; according to the formatting parameters. If this is not the case, an error message noting this is produced. This error message will cause the process to return a non-zero exit code. The test for this is made by comparing an MD5 hash value for the input and output code streams. This flag has no other effect on the functioning of perltidy. This might be useful for certain code maintenance operations. Note: you will not see this message if you have error messages turned off with the -quiet flag.

</dd>
<dt id="asu---assert-untidy">-asu, --assert-untidy</dt>
<dd>

This flag asserts that the input and output code streams are different, or in other words that the input code is &#39;untidy&#39; according to the formatting parameters. If this is not the case, an error message noting this is produced. This flag has no other effect on the functioning of perltidy.

</dd>
<dt id="sal-s---sub-alias-list-s">-sal=s, --sub-alias-list=s</dt>
<dd>

This flag causes one or more words to be treated the same as if they were the keyword &#39;sub&#39;. The string s contains one or more alias words, separated by spaces or commas.

For example,

<pre><code> perltidy -sal=&#39;method fun _sub M4&#39; </code></pre>

will cause the perltidy to treate the words &#39;method&#39;, &#39;fun&#39;, &#39;_sub&#39; and &#39;M4&#39; to be treated the same as if they were &#39;sub&#39;. Note that if the alias words are separated by spaces then the string of words should be placed in quotes.

Note that several other parameters accept a list of keywords, including &#39;sub&#39; (see <a href="#Specifying-Block-Types">&quot;Specifying Block Types&quot;</a>). You do not need to include any sub aliases in these lists. Just include keyword &#39;sub&#39; if you wish, and all aliases are automatically included.

</dd>
</dl>

<h1 id="FORMATTING-OPTIONS">FORMATTING OPTIONS</h1>

<h2 id="Basic-Options">Basic Options</h2>

<dl>

<dt id="notidy">--notidy</dt>
<dd>

This flag disables all formatting and causes the input to be copied unchanged to the output except for possible changes in line ending characters and any pre- and post-filters. This can be useful in conjunction with a hierarchical set of .perltidyrc files to avoid unwanted code tidying. See also <a href="#Skipping-Selected-Sections-of-Code">&quot;Skipping Selected Sections of Code&quot;</a> for a way to avoid tidying specific sections of code.

</dd>
<dt id="i-n---indent-columns-n">-i=n, --indent-columns=n</dt>
<dd>

Use n columns per indentation level (default n=4).

</dd>
<dt id="l-n---maximum-line-length-n">-l=n, --maximum-line-length=n</dt>
<dd>

The default maximum line length is n=80 characters. Perltidy will try to find line break points to keep lines below this length. However, long quotes and side comments may cause lines to exceed this length.

The default length of 80 comes from the past when this was the standard CRT screen width. Many programmers prefer to increase this to something like 120.

Setting -l=0 is equivalent to setting -l=(a very large number). But this is not recommended because, for example, a very long list will be formatted in a single long line.

</dd>
<dt id="vmll---variable-maximum-line-length">-vmll, --variable-maximum-line-length</dt>
<dd>

A problem arises using a fixed maximum line length with very deeply nested code and data structures because eventually the amount of leading whitespace used for indicating indentation takes up most or all of the available line width, leaving little or no space for the actual code or data. One solution is to use a vary long line length. Another solution is to use the -vmll flag, which basically tells perltidy to ignore leading whitespace when measuring the line length.

To be precise, when the -vmll parameter is set, the maximum line length of a line of code will be M+L*I, where

<pre><code> M is the value of --maximum-line-length=M (-l=M), default 80,
 I is the value of --indent-columns=I (-i=I), default 4,
 L is the indentation level of the line of code</code></pre>

When this flag is set, the choice of breakpoints for a block of code should be essentially independent of its nesting depth. However, the absolute line lengths, including leading whitespace, can still be arbitrarily large. This problem can be avoided by including the next parameter.

The default is not to do this (-nvmll).

</dd>
<dt id="wc-n---whitespace-cycle-n">-wc=n, --whitespace-cycle=n</dt>
<dd>

This flag also addresses problems with very deeply nested code and data structures. When the nesting depth exceeds the value n the leading whitespace will be reduced and start at a depth of 1 again. The result is that blocks of code will shift back to the left rather than moving arbitrarily far to the right. This occurs cyclically to any depth.

For example if one level of indentation equals 4 spaces (-i=4, the default), and one uses -wc=15, then if the leading whitespace on a line exceeds about 4*15=60 spaces it will be reduced back to 4*1=4 spaces and continue increasing from there. If the whitespace never exceeds this limit the formatting remains unchanged.

The combination of -vmll and -wc=n provides a solution to the problem of displaying arbitrarily deep data structures and code in a finite window, although -wc=n may of course be used without -vmll.

The default is not to use this, which can also be indicated using -wc=0.

</dd>
<dt id="tabs">tabs</dt>
<dd>

Using tab characters will almost certainly lead to future portability and maintenance problems, so the default and recommendation is not to use them. For those who prefer tabs, however, there are two different options.

Except for possibly introducing tab indentation characters, as outlined below, perltidy does not introduce any tab characters into your file, and it removes any tabs from the code (unless requested not to do so with -fws). If you have any tabs in your comments, quotes, or here-documents, they will remain.

<dl>

<dt id="et-n---entab-leading-whitespace">-et=n, --entab-leading-whitespace</dt>
<dd>

This flag causes each n initial space characters to be replaced by one tab character.

The value of the integer n can be any value but can be coordinated with the number of spaces used for intentation. For example, -et=4 -ci=4 -i=4 will produce one tab for each indentation level and and one for each continuation indentation level. You may want to coordinate the value of n with what your display software assumes for the spacing of a tab.

</dd>
<dt id="t---tabs">-t, --tabs</dt>
<dd>

This flag causes one leading tab character to be inserted for each level of indentation. Certain other features are incompatible with this option, and if these options are also given, then a warning message will be issued and this flag will be unset. One example is the -lp option. This flag is retained for backwards compatability, but if you use tabs, the -et=n flag is recommended.

</dd>
<dt id="dt-n---default-tabsize-n">-dt=n, --default-tabsize=n</dt>
<dd>

If the first line of code passed to perltidy contains leading tabs but no tab scheme is specified for the output stream then perltidy must guess how many spaces correspond to each leading tab. This number of spaces n corresponding to each leading tab of the input stream may be specified with -dt=n. The default is n=8.

This flag has no effect if a tab scheme is specified for the output stream, because then the input stream is assumed to use the same tab scheme and indentation spaces as for the output stream (any other assumption would lead to unstable editing).

</dd>
</dl>

</dd>
<dt id="syn---check-syntax">-syn, --check-syntax</dt>
<dd>

This flag is now ignored for safety, but the following documentation has been retained for reference.

This flag causes perltidy to run <code>perl -c -T</code> to check syntax of input and output. (To change the flags passed to perl, see the next item, -pscf). The results are written to the .LOG file, which will be saved if an error is detected in the output script. The output script is not checked if the input script has a syntax error. Perltidy does its own checking, but this option employs perl to get a &quot;second opinion&quot;.

If perl reports errors in the input file, they will not be reported in the error output unless the --warning-output flag is given.

The default is NOT to do this type of syntax checking (although perltidy will still do as much self-checking as possible). The reason is that it causes all code in BEGIN blocks to be executed, for all modules being used, and this opens the door to security issues and infinite loops when running perltidy.

</dd>
<dt id="pscf-s--perl-syntax-check-flags-s">-pscf=s, -perl-syntax-check-flags=s</dt>
<dd>

When perl is invoked to check syntax, the normal flags are <code>-c -T</code>. In addition, if the -x flag is given to perltidy, then perl will also be passed a -x flag. It should not normally be necessary to change these flags, but it can be done with the -pscf=s flag. For example, if the taint flag, <code>-T</code>, is not wanted, the flag could be set to be just -pscf=-c.

Perltidy will pass your string to perl with the exception that it will add a -c and -x if appropriate. The .LOG file will show exactly what flags were passed to perl.

</dd>
<dt id="xs---extended-syntax">-xs, --extended-syntax</dt>
<dd>

A problem with formatting Perl code is that some modules can introduce new syntax. This flag allows perltidy to handle certain common extensions to the standard syntax without complaint.

For example, without this flag a structure such as the following would generate a syntax error and the braces would not be balanced:

<pre><code> method deposit( Num $amount) {
 $self-&gt;balance( $self-&gt;balance + $amount );
 }</code></pre>

For one of the extensions, module Switch::Plain, colons are marked as labels. If you use this module, you may want to also use the --nooutdent-labels flag to prevent lines such as &#39;default:&#39; from being outdented.

This flag is enabled by default but it can be deactivated with -nxs. Probably the only reason to deactivate this flag is to generate more diagnostic messages when debugging a script.

</dd>
<dt id="io---indent-only">-io, --indent-only</dt>
<dd>

This flag is used to deactivate all whitespace and line break changes within non-blank lines of code. When it is in effect, the only change to the script will be to the indentation and to the number of blank lines. And any flags controlling whitespace and newlines will be ignored. You might want to use this if you are perfectly happy with your whitespace and line breaks, and merely want perltidy to handle the indentation. (This also speeds up perltidy by well over a factor of two, so it might be useful when perltidy is merely being used to help find a brace error in a large script).

Setting this flag is equivalent to setting --freeze-newlines and --freeze-whitespace.

If you also want to keep your existing blank lines exactly as they are, you can add --freeze-blank-lines.

With this option perltidy is still free to modify the indenting (and outdenting) of code and comments as it normally would. If you also want to prevent long comment lines from being outdented, you can add either -noll or -l=0.

Setting this flag will prevent perltidy from doing any special operations on closing side comments. You may still delete all side comments however when this flag is in effect.

</dd>
<dt id="enc-s---character-encoding-s">-enc=s, --character-encoding=s</dt>
<dd>

This flag indicates the character encoding, if any, of the input data stream. Perltidy does not look for the encoding directives in the soure stream, such as use utf8, and instead relies on this flag to determine the encoding. (Note that perltidy often works on snippets of code rather than complete files so it cannot rely on use utf8 directives).

The possible values for s are (1) the name of an encoding recognized by the Encode.pm module, (2) none if no encoding is used, or (3) &lt;guess&gt; if perltidy should guess.

For example, the value utf8 causes the stream to be read and written as UTF-8. If the input stream cannot be decoded with a specified encoding then processing is not done.

The value none causes the stream to be processed without special encoding assumptions. This is appropriate for files which are written in single-byte character encodings such as latin-1.

The value guess tells perltidy to guess between either utf8 encoding or no encoding (meaning one character per byte). The guess uses the Encode::Guess module and this restricted range of guesses covers the most common cases. Testing showed that considering any greater number of encodings as guess suspects is too risky.

The current default is guess.

The abbreviations -utf8 or -UTF8 are equivalent to -enc=utf8, and the abbreviation -guess is equivalent to &lt;-enc=guess&gt;. So to process a file named file.pl which is encoded in UTF-8 you can use:

<pre><code> perltidy -utf8 file.pl</code></pre>

or perltidy -guess file.pl

To process a file in euc-jp you could use

<pre><code> perltidy -enc=euc-jp file.pl</code></pre>

A perltidy output file is unencoded if the input file is unencoded, and otherwise it is encoded as utf8, even if the input encoding was not utf8.

</dd>
<dt id="gcs---use-unicode-gcstring">-gcs, --use-unicode-gcstring</dt>
<dd>

This flag controls whether or not perltidy may use module Unicode::GCString to obtain accurate display widths of wide characters. The default is --nouse-unicode-gcstring.

If this flag is set, and text is encoded, perltidy will look for the module Unicode::GCString and, if found, will use it to obtain 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 set this flag and also to install Unicode::GCString separately.

If this flag is set and perltidy does not find module Unicode::GCString, a warning message will be produced and processing will continue but without the potential benefit provided by the module.

Also note that actual vertical alignment depends upon the fonts used by the text display software, so vertical alignment may not be optimal even when Unicode::GCString is used.

</dd>
<dt id="ole-s---output-line-ending-s">-ole=s, --output-line-ending=s</dt>
<dd>

where s=<code>win</code>, <code>dos</code>, <code>unix</code>, or <code>mac</code>. This flag tells perltidy to output line endings for a specific system. Normally, perltidy writes files with the line separator character of the host system. The <code>win</code> and <code>dos</code> flags have an identical result.

</dd>
<dt id="ple---preserve-line-endings">-ple, --preserve-line-endings</dt>
<dd>

This flag tells perltidy to write its output files with the same line endings as the input file, if possible. It should work for dos, unix, and mac line endings. It will only work if perltidy input comes from a filename (rather than stdin, for example). If perltidy has trouble determining the input file line ending, it will revert to the default behavior of using the line ending of the host system.

</dd>
<dt id="it-n---iterations-n">-it=n, --iterations=n</dt>
<dd>

This flag causes perltidy to do n complete iterations. The reason for this flag is that code beautification is an iterative process and in some cases the output from perltidy can be different if it is applied a second time. For most purposes the default of n=1 should be satisfactory. However n=2 can be useful when a major style change is being made, or when code is being beautified on check-in to a source code control system. It has been found to be extremely rare for the output to change after 2 iterations. If a value n is greater than 2 is input then a convergence test will be used to stop the iterations as soon as possible, almost always after 2 iterations. See the next item for a simplified iteration control.

This flag has no effect when perltidy is used to generate html.

</dd>
<dt id="conv---converge">-conv, --converge</dt>
<dd>

This flag is equivalent to -it=4 and is included to simplify iteration control. For all practical purposes one either does or does not want to be sure that the output is converged, and there is no penalty to using a large iteration limit since perltidy will check for convergence and stop iterating as soon as possible. The default is -nconv (no convergence check). Using -conv will approximately double run time since typically one extra iteration is required to verify convergence. No extra iterations are required if no new line breaks are made, and two extra iterations are occasionally needed when reformatting complex code structures, such as deeply nested ternary statements.

</dd>
</dl>

<h2 id="Code-Indentation-Control">Code Indentation Control</h2>

<dl>

<dt id="ci-n---continuation-indentation-n">-ci=n, --continuation-indentation=n</dt>
<dd>

Continuation indentation is extra indentation spaces applied when a long line is broken. The default is n=2, illustrated here:

<pre><code> my $level = # -ci=2 
 ( $max_index_to_go &gt;= 0 ) ? $levels_to_go[0] : $last_output_level;</code></pre>

The same example, with n=0, is a little harder to read:

<pre><code> my $level = # -ci=0 
 ( $max_index_to_go &gt;= 0 ) ? $levels_to_go[0] : $last_output_level;</code></pre>

The value given to -ci is also used by some commands when a small space is required. Examples are commands for outdenting labels, -ola, and control keywords, -okw.

When default values are not used, it is recommended that either

(1) the value n given with -ci=n be no more than about one-half of the number of spaces assigned to a full indentation level on the -i=n command, or

(2) the flag -extended-continuation-indentation is used (see next section).

</dd>
<dt id="xci---extended-continuation-indentation">-xci, --extended-continuation-indentation</dt>
<dd>

This flag allows perltidy to use some improvements which have been made to its indentation model. One of the things it does is &quot;extend&quot; continuation indentation deeper into structures, hence the name. The improved indentation is particularly noticable when the flags -ci=n and -i=n use the same value of n. There are no significant disadvantages to using this flag, but to avoid disturbing existing formatting the default is not to use it, -nxci.

Please see the section <a href="#pbp---perl-best-practices">&quot;-pbp, --perl-best-practices&quot;</a> for an example of how this flag can improve the formatting of ternary statements. It can also improve indentation of some multi-line qw lists as shown below.

<pre><code> # perltidy
 foreach $color (
 qw(
 AntiqueWhite3 Bisque1 Bisque2 Bisque3 Bisque4
 SlateBlue3 RoyalBlue1 SteelBlue2 DeepSkyBlue3
 ),
 qw(
 LightBlue1 DarkSlateGray1 Aquamarine2 DarkSeaGreen2
 SeaGreen1 Yellow1 IndianRed1 IndianRed2 Tan1 Tan4
 )
 )

# perltidy -xci
 foreach $color (
 qw(
 AntiqueWhite3 Bisque1 Bisque2 Bisque3 Bisque4
 SlateBlue3 RoyalBlue1 SteelBlue2 DeepSkyBlue3
 ),
 qw(
 LightBlue1 DarkSlateGray1 Aquamarine2 DarkSeaGreen2
 SeaGreen1 Yellow1 IndianRed1 IndianRed2 Tan1 Tan4
 )
 )</code></pre>

</dd>
<dt id="sil-n---starting-indentation-level-n">-sil=n --starting-indentation-level=n</dt>
<dd>

By default, perltidy examines the input file and tries to determine the starting indentation level. While it is often zero, it may not be zero for a code snippet being sent from an editing session.

To guess the starting indentation level perltidy simply assumes that indentation scheme used to create the code snippet is the same as is being used for the current perltidy process. This is the only sensible guess that can be made. It should be correct if this is true, but otherwise it probably won&#39;t. For example, if the input script was written with -i=2 and the current peltidy flags have -i=4, the wrong initial indentation will be guessed for a code snippet which has non-zero initial indentation. Likewise, if an entabbing scheme is used in the input script and not in the current process then the guessed indentation will be wrong.

If the default method does not work correctly, or you want to change the starting level, use -sil=n, to force the starting level to be n.

</dd>
<dt id="List-indentation-using--lp---line-up-parentheses">List indentation using -lp, --line-up-parentheses</dt>
<dd>

By default, perltidy indents lists with 4 spaces, or whatever value is specified with -i=n. Here is a small list formatted in this way:

<pre><code> # perltidy (default)
 @month_of_year = (
 &#39;Jan&#39;, &#39;Feb&#39;, &#39;Mar&#39;, &#39;Apr&#39;, &#39;May&#39;, &#39;Jun&#39;,
 &#39;Jul&#39;, &#39;Aug&#39;, &#39;Sep&#39;, &#39;Oct&#39;, &#39;Nov&#39;, &#39;Dec&#39;
 );</code></pre>

Use the -lp flag to add extra indentation to cause the data to begin past the opening parentheses of a sub call or list, or opening square bracket of an anonymous array, or opening curly brace of an anonymous hash. With this option, the above list would become:

<pre><code> # perltidy -lp
 @month_of_year = (
 &#39;Jan&#39;, &#39;Feb&#39;, &#39;Mar&#39;, &#39;Apr&#39;, &#39;May&#39;, &#39;Jun&#39;,
 &#39;Jul&#39;, &#39;Aug&#39;, &#39;Sep&#39;, &#39;Oct&#39;, &#39;Nov&#39;, &#39;Dec&#39;
 );</code></pre>

If the available line length (see -l=n ) does not permit this much space, perltidy will use less. For alternate placement of the closing paren, see the next section.

This option has no effect on code BLOCKS, such as if/then/else blocks, which always use whatever is specified with -i=n. Also, the existence of line breaks and/or block comments between the opening and closing parens may cause perltidy to temporarily revert to its default method.

Note: The -lp option may not be used together with the -t tabs option. It may, however, be used with the -et=n tab method.

In addition, any parameter which significantly restricts the ability of perltidy to choose newlines will conflict with -lp and will cause -lp to be deactivated. These include -io, -fnl, -nanl, and -ndnl. The reason is that the -lp indentation style can require the careful coordination of an arbitrary number of break points in hierarchical lists, and these flags may prevent that.

</dd>
<dt id="cti-n---closing-token-indentation">-cti=n, --closing-token-indentation</dt>
<dd>

The -cti=n flag controls the indentation of a line beginning with a <code>)</code>, <code>]</code>, or a non-block <code>}</code>. Such a line receives:

<pre><code> -cti = 0 no extra indentation (default)
 -cti = 1 extra indentation such that the closing token
 aligns with its opening token.
 -cti = 2 one extra indentation level if the line looks like:
 ); or ]; or };
 -cti = 3 one extra indentation level always</code></pre>

The flags -cti=1 and -cti=2 work well with the -lp flag (previous section).

<pre><code> # perltidy -lp -cti=1
 @month_of_year = (
 &#39;Jan&#39;, &#39;Feb&#39;, &#39;Mar&#39;, &#39;Apr&#39;, &#39;May&#39;, &#39;Jun&#39;,
 &#39;Jul&#39;, &#39;Aug&#39;, &#39;Sep&#39;, &#39;Oct&#39;, &#39;Nov&#39;, &#39;Dec&#39;
 );

# perltidy -lp -cti=2
 @month_of_year = (
 &#39;Jan&#39;, &#39;Feb&#39;, &#39;Mar&#39;, &#39;Apr&#39;, &#39;May&#39;, &#39;Jun&#39;,
 &#39;Jul&#39;, &#39;Aug&#39;, &#39;Sep&#39;, &#39;Oct&#39;, &#39;Nov&#39;, &#39;Dec&#39;
 );</code></pre>

These flags are merely hints to the formatter and they may not always be followed. In particular, if -lp is not being used, the indentation for cti=1 is constrained to be no more than one indentation level.

If desired, this control can be applied independently to each of the closing container token types. In fact, -cti=n is merely an abbreviation for -cpi=n -csbi=n -cbi=n, where: -cpi or --closing-paren-indentation controls )&#39;s, -csbi or --closing-square-bracket-indentation controls ]&#39;s, -cbi or --closing-brace-indentation controls non-block }&#39;s.

</dd>
<dt id="icp---indent-closing-paren">-icp, --indent-closing-paren</dt>
<dd>

The -icp flag is equivalent to -cti=2, described in the previous section. The -nicp flag is equivalent -cti=0. They are included for backwards compatibility.

</dd>
<dt id="icb---indent-closing-brace">-icb, --indent-closing-brace</dt>
<dd>

The -icb option gives one extra level of indentation to a brace which terminates a code block . For example,

The default is not to do this, indicated by -nicb.

</dd>
<dt id="nib---non-indenting-braces">-nib, --non-indenting-braces</dt>
<dd>

Normally, lines of code contained within a pair of block braces receive one additional level of indentation. This flag, which is enabled by default, causes perltidy to look for opening block braces which are followed by a special side comment. This special side comment is #&lt;&lt;&lt; by default. If found, the code between this opening brace and its corresponding closing brace will not be given the normal extra indentation level. For example:

<pre><code> { #&lt;&lt;&lt; a closure to contain lexical vars

my $var;  # this line does not get one level of indentation
            ...

}

# this line does not &#39;see&#39; $var;</code></pre>

This can be useful, for example, when combining code from different files. Different sections of code can be placed within braces to keep their lexical variables from being visible to the end of the file. To keep the new braces from causing all of their contained code to be indented if you run perltidy, and possibly introducing new line breaks in long lines, you can mark the opening braces with this special side comment.

Only the opening brace needs to be marked, since perltidy knows where the closing brace is. Braces contained within marked braces may also be marked as non-indenting.

If your code happens to have some opening braces followed by &#39;#&lt;&lt;&lt;&#39;, and you don&#39;t want this behavior, you can use -nnib to deactivate it. To make it easy to remember, the default string is the same as the string for starting a format-skipping section. There is no confusion because in that case it is for a block comment rather than a side-comment.

The special side comment can be changed with the next parameter.

</dd>
<dt id="nibp-s---non-indenting-brace-prefix-s">-nibp=s, --non-indenting-brace-prefix=s</dt>
<dd>

The -nibp=string parameter may be used to change the marker for non-indenting braces. The default is equivalent to -nibp=&#39;#&lt;&lt;&lt;&#39;. The string that you enter must begin with a # and should be in quotes as necessary to get past the command shell of your system. This string is the leading text of a regex pattern that is constructed by appending pre-pending a &#39;^&#39; and appending a&#39;\s&#39;, so you must also include backslashes for characters to be taken literally rather than as patterns.

For example, to match the side comment &#39;#++&#39;, the parameter would be

</dd>
<dt id="olq---outdent-long-quotes">-olq, --outdent-long-quotes</dt>
<dd>

When -olq is set, lines which is a quoted string longer than the value maximum-line-length will have their indentation removed to make them more readable. This is the default. To prevent such out-denting, use -nolq or --nooutdent-long-lines.

</dd>
<dt id="oll---outdent-long-lines">-oll, --outdent-long-lines</dt>
<dd>

This command is equivalent to --outdent-long-quotes and --outdent-long-comments, and it is included for compatibility with previous versions of perltidy. The negation of this also works, -noll or --nooutdent-long-lines, and is equivalent to setting -nolq and -nolc.

</dd>
<dt id="Outdenting-Labels:--ola---outdent-labels">Outdenting Labels: -ola, --outdent-labels</dt>
<dd>

This command will cause labels to be outdented by 2 spaces (or whatever -ci has been set to), if possible. This is the default. For example:

<pre><code> my $i;
 LOOP: while ( $i = &lt;FOTOS&gt; ) {
 chomp($i);
 next unless $i;
 fixit($i);
 }</code></pre>

Use -nola to not outdent labels.

</dd>
<dt id="Outdenting-Keywords">Outdenting Keywords</dt>
<dd>

<dl>

<dt id="okw---outdent-keywords">-okw, --outdent-keywords</dt>
<dd>

The command -okw will cause certain leading control keywords to be outdented by 2 spaces (or whatever -ci has been set to), if possible. By default, these keywords are <code>redo</code>, <code>next</code>, <code>last</code>, <code>goto</code>, and <code>return</code>. The intention is to make these control keywords easier to see. To change this list of keywords being outdented, see the next section.

For example, using <code>perltidy -okw</code> on the previous example gives:

<pre><code> my $i;
 LOOP: while ( $i = &lt;FOTOS&gt; ) {
 chomp($i);
 next unless $i;
 fixit($i);
 }</code></pre>

The default is not to do this.

</dd>
<dt id="Specifying-Outdented-Keywords:--okwl-string---outdent-keyword-list-string">Specifying Outdented Keywords: -okwl=string, --outdent-keyword-list=string</dt>
<dd>

This command can be used to change the keywords which are outdented with the -okw command. The parameter string is a required list of perl keywords, which should be placed in quotes if there are more than one. By itself, it does not cause any outdenting to occur, so the -okw command is still required.

For example, the commands <code>-okwl=&quot;next last redo goto&quot; -okw</code> will cause those four keywords to be outdented. It is probably simplest to place any -okwl command in a .perltidyrc file.

</dd>
</dl>

<h2 id="Whitespace-Control">Whitespace Control</h2>

Whitespace refers to the blank space between variables, operators, and other code tokens.

<dl>

<dt id="fws---freeze-whitespace">-fws, --freeze-whitespace</dt>
<dd>

This flag causes your original whitespace to remain unchanged, and causes the rest of the whitespace commands in this section, the Code Indentation section, and the Comment Control section to be ignored.

</dd>
<dt id="Tightness-of-curly-braces-parentheses-and-square-brackets">Tightness of curly braces, parentheses, and square brackets.</dt>
<dd>

Here the term &quot;tightness&quot; will mean the closeness with which pairs of enclosing tokens, such as parentheses, contain the quantities within. A numerical value of 0, 1, or 2 defines the tightness, with 0 being least tight and 2 being most tight. Spaces within containers are always symmetric, so if there is a space after a <code>(</code> then there will be a space before the corresponding <code>)</code>.

The -pt=n or --paren-tightness=n parameter controls the space within parens. The example below shows the effect of the three possible values, 0, 1, and 2:

<pre><code> if ( ( my $len_tab = length( $tabstr ) ) &gt; 0 ) { # -pt=0
 if ( ( my $len_tab = length($tabstr) ) &gt; 0 ) { # -pt=1 (default)
 if ((my $len_tab = length($tabstr)) &gt; 0) { # -pt=2</code></pre>

When n is 0, there is always a space to the right of a &#39;(&#39; and to the left of a &#39;)&#39;. For n=2 there is never a space. For n=1, the default, there is a space unless the quantity within the parens is a single token, such as an identifier or quoted string.

Likewise, the parameter -sbt=n or --square-bracket-tightness=n controls the space within square brackets, as illustrated below.

<pre><code> $width = $col[ $j + $k ] - $col[ $j ]; # -sbt=0
 $width = $col[ $j + $k ] - $col[$j]; # -sbt=1 (default)
 $width = $col[$j + $k] - $col[$j]; # -sbt=2 </code></pre>

Curly braces which do not contain code blocks are controlled by the parameter -bt=n or --brace-tightness=n.

<pre><code> $obj-&gt;{ $parsed_sql-&gt;{ &#39;table&#39; }[0] }; # -bt=0
 $obj-&gt;{ $parsed_sql-&gt;{&#39;table&#39;}[0] }; # -bt=1 (default)
 $obj-&gt;{$parsed_sql-&gt;{&#39;table&#39;}[0]}; # -bt=2</code></pre>

And finally, curly braces which contain blocks of code are controlled by the parameter -bbt=n or --block-brace-tightness=n as illustrated in the example below.

<pre><code> %bf = map { $_ =&gt; -M $_ } grep { /\.deb$/ } dirents &#39;.&#39;; # -bbt=0 (default)
 %bf = map { $_ =&gt; -M $_ } grep {/\.deb$/} dirents &#39;.&#39;; # -bbt=1
 %bf = map {$_ =&gt; -M $_} grep {/\.deb$/} dirents &#39;.&#39;; # -bbt=2</code></pre>

To simplify input in the case that all of the tightness flags have the same value &lt;n&gt;, the parameter &lt;-act=n&gt; or --all-containers-tightness=n is an abbreviation for the combination &lt;-pt=n -sbt=n -bt=n -bbt=n&gt;.

</dd>
<dt id="tso---tight-secret-operators">-tso, --tight-secret-operators</dt>
<dd>

The flag -tso causes certain perl token sequences (secret operators) which might be considered to be a single operator to be formatted &quot;tightly&quot; (without spaces). The operators currently modified by this flag are:

For example the sequence 0 +, which converts a string to a number, would be formatted without a space: 0+ when the -tso flag is set. This flag is off by default.

</dd>
<dt id="sts---space-terminal-semicolon">-sts, --space-terminal-semicolon</dt>
<dd>

Some programmers prefer a space before all terminal semicolons. The default is for no such space, and is indicated with -nsts or --nospace-terminal-semicolon.

<pre><code> $i = 1 ; # -sts
 $i = 1; # -nsts (default)</code></pre>

</dd>
<dt id="sfs---space-for-semicolon">-sfs, --space-for-semicolon</dt>
<dd>

Semicolons within for loops may sometimes be hard to see, particularly when commas are also present. This option places spaces on both sides of these special semicolons, and is the default. Use -nsfs or --nospace-for-semicolon to deactivate it.

<pre><code> for ( @a = @$ap, $u = shift @a ; @a ; $u = $v ) { # -sfs (default)
 for ( @a = @$ap, $u = shift @a; @a; $u = $v ) { # -nsfs</code></pre>

</dd>
<dt id="asc---add-semicolons">-asc, --add-semicolons</dt>
<dd>

Setting -asc allows perltidy to add any missing optional semicolon at the end of a line which is followed by a closing curly brace on the next line. This is the default, and may be deactivated with -nasc or --noadd-semicolons.

</dd>
<dt id="dsm---delete-semicolons">-dsm, --delete-semicolons</dt>
<dd>

Setting -dsm allows perltidy to delete extra semicolons which are simply empty statements. This is the default, and may be deactivated with -ndsm or --nodelete-semicolons. (Such semicolons are not deleted, however, if they would promote a side comment to a block comment).

</dd>
<dt id="aws---add-whitespace">-aws, --add-whitespace</dt>
<dd>

Setting this option allows perltidy to add certain whitespace to improve code readability. This is the default. If you do not want any whitespace added, but are willing to have some whitespace deleted, use -naws. (Use -fws to leave whitespace completely unchanged).

</dd>
<dt id="dws---delete-old-whitespace">-dws, --delete-old-whitespace</dt>
<dd>

Setting this option allows perltidy to remove some old whitespace between characters, if necessary. This is the default. If you do not want any old whitespace removed, use -ndws or --nodelete-old-whitespace.

</dd>
<dt id="Detailed-whitespace-controls-around-tokens">Detailed whitespace controls around tokens</dt>
<dd>

For those who want more detailed control over the whitespace around tokens, there are four parameters which can directly modify the default whitespace rules built into perltidy for any token. They are:

-wls=s or --want-left-space=s,

-nwls=s or --nowant-left-space=s,

-wrs=s or --want-right-space=s,

-nwrs=s or --nowant-right-space=s.

These parameters are each followed by a quoted string, s, containing a list of token types. No more than one of each of these parameters should be specified, because repeating a command-line parameter always overwrites the previous one before perltidy ever sees it.

To illustrate how these are used, suppose it is desired that there be no space on either side of the token types = + - / *. The following two parameters would specify this desire:

(Note that the token types are in quotes, and that they are separated by spaces). With these modified whitespace rules, the following line of math:

becomes this:

These parameters should be considered to be hints to perltidy rather than fixed rules, because perltidy must try to resolve conflicts that arise between them and all of the other rules that it uses. One conflict that can arise is if, between two tokens, the left token wants a space and the right one doesn&#39;t. In this case, the token not wanting a space takes priority.

It is necessary to have a list of all token types in order to create this type of input. Such a list can be obtained by the command --dump-token-types. Also try the -D flag on a short snippet of code and look at the .DEBUG file to see the tokenization.

WARNING Be sure to put these tokens in quotes to avoid having them misinterpreted by your command shell.

</dd>
<dt id="Note1:-Perltidy-does-always-follow-whitespace-controls">Note1: Perltidy does always follow whitespace controls</dt>
<dd>

The various parameters controlling whitespace within a program are requests which perltidy follows as well as possible, but there are a number of situations where changing whitespace could change program behavior and is not done. Some of these are obvious; for example, we should not remove the space between the two plus symbols in &#39;$x+ +$y&#39; to avoid creating a &#39;++&#39; operator. Some are more subtle and involve the whitespace around bareword symbols and locations of possible filehandles. For example, consider the problem of formatting the following subroutine:

<pre><code> sub print_div {
 my ($x,$y)=@_;
 print $x/$y;
 }</code></pre>

Suppose the user requests that / signs have a space to the left but not to the right. Perltidy will refuse to do this, but if this were done the result would be

<pre><code> sub print_div {
 my ($x,$y)=@_;
 print $x /$y;
 }</code></pre>

If formatted in this way, the program will not run (at least with recent versions of perl) because the $x is taken to be a filehandle and / is assumed to start a quote. In a complex program, there might happen to be a / which terminates the multiline quote without a syntax error, allowing the program to run, but not as intended.

Related issues arise with other binary operator symbols, such as + and -, and in older versions of perl there could be problems with ternary operators. So to avoid changing program behavior, perltidy has the simple rule that whitespace around possible filehandles is left unchanged. Likewise, whitespace around barewords is left unchanged. The reason is that if the barewords are defined in other modules, or in code that has not even been written yet, perltidy will not have seen their prototypes and must treat them cautiously.

In perltidy this is implemented in the tokenizer by marking token following a print keyword as a special type Z. When formatting is being done, whitespace following this token type is generally left unchanged as a precaution against changing program behavior. This is excessively conservative but simple and easy to implement. Keywords which are treated similarly to print include printf, sort, exec, system. Changes in spacing around parameters following these keywords may have to be made manually. For example, the space, or lack of space, after the parameter $foo in the following line will be unchanged in formatting.

<pre><code> system($foo );
 system($foo);</code></pre>

To find if a token is of type Z you can use perltidy -DEBUG. For the first line above the result is

<pre><code> 1: system($foo );
 1: kkkkkk{ZZZZb};</code></pre>

which shows that system is type k (keyword) and $foo is type Z.

</dd>
<dt id="Note2:-Perltidys-whitespace-rules-are-not-perfect">Note2: Perltidy&#39;s whitespace rules are not perfect</dt>
<dd>

Despite these precautions, it is still possible to introduce syntax errors with some asymmetric whitespace rules, particularly when call parameters are not placed in containg parens or braces. For example, the following two lines will be parsed by perl without a syntax error:

<pre><code> # original programming, syntax ok
 my @newkeys = map $_-$nrecs+@data, @oldkeys;

# perltidy default, syntax ok
 my @newkeys = map $_ - $nrecs + @data, @oldkeys;</code></pre>

But the following will give a syntax error:

<pre><code> # perltidy -nwrs=&#39;-&#39;
 my @newkeys = map $_ -$nrecs + @data, @oldkeys;</code></pre>

For another example, the following two lines will be parsed without syntax error:

<pre><code> # original programming, syntax ok
 for my $severity ( reverse $SEVERITY_LOWEST+1 .. $SEVERITY_HIGHEST ) { ... }

# perltidy default, syntax ok
 for my $severity ( reverse $SEVERITY_LOWEST + 1 .. $SEVERITY_HIGHEST ) { ... }</code></pre>

But the following will give a syntax error:

<pre><code> # perltidy -nwrs=&#39;+&#39;, syntax error:
 for my $severity ( reverse $SEVERITY_LOWEST +1 .. $SEVERITY_HIGHEST ) { ... }</code></pre>

To avoid subtle parsing problems like this, it is best to avoid spacing a binary operator asymetrically with a space on the left but not on the right.

</dd>
<dt id="Space-between-specific-keywords-and-opening-paren">Space between specific keywords and opening paren</dt>
<dd>

When an opening paren follows a Perl keyword, no space is introduced after the keyword, unless it is (by default) one of these:

<pre><code> my local our and or xor eq ne if else elsif until unless 
 while for foreach return switch case given when</code></pre>

These defaults can be modified with two commands:

-sak=s or --space-after-keyword=s adds keywords.

-nsak=s or --nospace-after-keyword=s removes keywords.

where s is a list of keywords (in quotes if necessary). For example,

<pre><code> my ( $a, $b, $c ) = @_; # default
 my( $a, $b, $c ) = @_; # -nsak=&quot;my local our&quot;</code></pre>

The abbreviation -nsak=&#39;*&#39; is equivalent to including all of the keywords in the above list.

When both -nsak=s and -sak=s commands are included, the -nsak=s command is executed first. For example, to have space after only the keywords (my, local, our) you could use -nsak=&quot;*&quot; -sak=&quot;my local our&quot;.

To put a space after all keywords, see the next item.

</dd>
<dt id="Space-between-all-keywords-and-opening-parens">Space between all keywords and opening parens</dt>
<dd>

When an opening paren follows a function or keyword, no space is introduced after the keyword except for the keywords noted in the previous item. To always put a space between a function or keyword and its opening paren, use the command:

-skp or --space-keyword-paren

You may also want to use the flag -sfp (next item) too.

</dd>
<dt id="Space-between-all-function-names-and-opening-parens">Space between all function names and opening parens</dt>
<dd>

When an opening paren follows a function the default and recommended formatting is not to introduce a space. To cause a space to be introduced use:

-sfp or --space-function-paren

<pre><code> myfunc( $a, $b, $c ); # default 
 myfunc ( $a, $b, $c ); # -sfp</code></pre>

You will probably also want to use the flag -skp (previous item) too.

The reason this is not recommended is that spacing a function paren can make a program vulnerable to parsing problems by Perl. For example, the following two-line program will run as written but will have a syntax error if reformatted with -sfp:

<pre><code> if ( -e filename() ) { print &quot;I&#39;m here\n&quot;; }
 sub filename { return $0 }</code></pre>

In this particular case the syntax error can be removed if the line order is reversed, so that Perl parses &#39;sub filename&#39; first.

</dd>
<dt id="spp-n-or---space-prototype-paren-n">-spp=n or --space-prototype-paren=n</dt>
<dd>

This flag can be used to control whether a function prototype is preceded by a space. For example, the following prototype does not have a space.

<pre><code> sub usage();</code></pre>

This integer n may have the value 0, 1, or 2 as follows:

<pre><code> -spp=0 means no space before the paren
 -spp=1 means follow the example of the source code [DEFAULT]
 -spp=2 means always put a space before the paren</code></pre>

The default is -spp=1, meaning that a space will be used if and only if there is one in the source code. Given the above line of code, the result of applying the different options would be:

<pre><code> sub usage(); # n=0 [no space]
 sub usage(); # n=1 [default; follows input]
 sub usage (); # n=2 [space]</code></pre>

</dd>
<dt id="kpit-n-or---keyword-paren-inner-tightness-n">-kpit=n or --keyword-paren-inner-tightness=n</dt>
<dd>

The space inside of an opening paren, which itself follows a certain keyword, can be controlled by this parameter. The space on the inside of the corresponding closing paren will be treated in the same (balanced) manner. This parameter has precedence over any other paren spacing rules. The values of n are as follows:

<pre><code> -kpit=0 means always put a space (not tight)
 -kpit=1 means ignore this parameter [default]
 -kpit=2 means never put a space (tight)</code></pre>

To illustrate, the following snippet is shown formatted in three ways:

<pre><code> if ( seek( DATA, 0, 0 ) ) { ... } # perltidy (default)
 if (seek(DATA, 0, 0)) { ... } # perltidy -pt=2
 if ( seek(DATA, 0, 0) ) { ... } # perltidy -pt=2 -kpit=0</code></pre>

In the second case the -pt=2 parameter makes all of the parens tight. In the third case the -kpit=0 flag causes the space within the &#39;if&#39; parens to have a space, since &#39;if&#39; is one of the keywords to which the -kpit flag applies by default. The remaining parens are still tight because of the -pt=2 parameter.

The set of keywords to which this parameter applies are by default are:

<pre><code> if elsif unless while until for foreach</code></pre>

These can be changed with the parameter -kpitl=s described in the next section.

</dd>
<dt id="kpitl-string-or---keyword-paren-inner-tightness-string">-kpitl=string or --keyword-paren-inner-tightness=string</dt>
<dd>

This command can be used to change the keywords to which the the -kpit=n command applies. The parameter string is a required list either keywords or functions, which should be placed in quotes if there are more than one. By itself, this parameter does not cause any change in spacing, so the -kpit=n command is still required.

For example, the commands <code>-kpitl=&quot;if else while&quot; -kpit=2</code> will cause the just the spaces inside parens following &#39;if&#39;, &#39;else&#39;, and &#39;while&#39; keywords to follow the tightness value indicated by the -kpit=2 flag.

</dd>
<dt id="lop-or---logical-padding">-lop or --logical-padding</dt>
<dd>

In the following example some extra space has been inserted on the second line between the two open parens. This extra space is called &quot;logical padding&quot; and is intended to help align similar things vertically in some logical or ternary expressions.

<pre><code> # perltidy [default formatting] 
 $same =
 ( ( $aP eq $bP )
 &amp;&amp; ( $aS eq $bS )
 &amp;&amp; ( $aT eq $bT )
 &amp;&amp; ( $a-&gt;{&#39;title&#39;} eq $b-&gt;{&#39;title&#39;} )
 &amp;&amp; ( $a-&gt;{&#39;href&#39;} eq $b-&gt;{&#39;href&#39;} ) );</code></pre>

Note that this is considered to be a different operation from &quot;vertical alignment&quot; because space at just one line is being adjusted, whereas in &quot;vertical alignment&quot; the spaces at all lines are being adjusted. So it sort of a local version of vertical alignment.

Here is an example involving a ternary operator:

<pre><code> # perltidy [default formatting] 
 $bits =
 $top &gt; 0xffff ? 32
 : $top &gt; 0xff ? 16
 : $top &gt; 1 ? 8
 : 1;</code></pre>

This behavior is controlled with the flag --logical-padding, which is set &#39;on&#39; by default. If it is not desired it can be turned off using --nological-padding or -nlop. The above two examples become, with -nlop:

<pre><code> # perltidy -nlop
 $same =
 ( ( $aP eq $bP )
 &amp;&amp; ( $aS eq $bS )
 &amp;&amp; ( $aT eq $bT )
 &amp;&amp; ( $a-&gt;{&#39;title&#39;} eq $b-&gt;{&#39;title&#39;} )
 &amp;&amp; ( $a-&gt;{&#39;href&#39;} eq $b-&gt;{&#39;href&#39;} ) );

# perltidy -nlop
 $bits =
 $top &gt; 0xffff ? 32
 : $top &gt; 0xff ? 16
 : $top &gt; 1 ? 8
 : 1;</code></pre>

</dd>
<dt id="Trimming-whitespace-around-qw-quotes">Trimming whitespace around <code>qw</code> quotes</dt>
<dd>

-tqw or --trim-qw provide the default behavior of trimming spaces around multi-line <code>qw</code> quotes and indenting them appropriately.

-ntqw or --notrim-qw cause leading and trailing whitespace around multi-line <code>qw</code> quotes to be left unchanged. This option will not normally be necessary, but was added for testing purposes, because in some versions of perl, trimming <code>qw</code> quotes changes the syntax tree.

</dd>
<dt id="b-sbq-n-or-b--space-backslash-quote-n">b&lt;-sbq=n&gt; or b&lt;--space-backslash-quote=n&gt;</dt>
<dd>

lines like

<pre><code> $str1=\&quot;string1&quot;;
 $str2=\&#39;string2&#39;;</code></pre>

can confuse syntax highlighters unless a space is included between the backslash and the single or double quotation mark.

this can be controlled with the value of b&lt;n&gt; as follows:

<pre><code> -sbq=0 means no space between the backslash and quote
 -sbq=1 means follow the example of the source code
 -sbq=2 means always put a space between the backslash and quote</code></pre>

The default is -sbq=1, meaning that a space will be used if there is one in the source code.

</dd>
<dt id="Trimming-trailing-whitespace-from-lines-of-POD">Trimming trailing whitespace from lines of POD</dt>
<dd>

-trp or --trim-pod will remove trailing whitespace from lines of POD. The default is not to do this.

</dd>
</dl>

<h2 id="Comment-Controls">Comment Controls</h2>

Perltidy has a number of ways to control the appearance of both block comments and side comments. The term block comment here refers to a full-line comment, whereas side comment will refer to a comment which appears on a line to the right of some code.

<dl>

<dt id="ibc---indent-block-comments">-ibc, --indent-block-comments</dt>
<dd>

Block comments normally look best when they are indented to the same level as the code which follows them. This is the default behavior, but you may use -nibc to keep block comments left-justified. Here is an example:

<pre><code> # this comment is indented (-ibc, default)
 if ($task) { yyy(); }</code></pre>

The alternative is -nibc:

<pre><code> # this comment is not indented (-nibc)
 if ($task) { yyy(); }</code></pre>

See also the next item, -isbc, as well as -sbc, for other ways to have some indented and some outdented block comments.

</dd>
<dt id="isbc---indent-spaced-block-comments">-isbc, --indent-spaced-block-comments</dt>
<dd>

If there is no leading space on the line, then the comment will not be indented, and otherwise it may be.

If both -ibc and -isbc are set, then -isbc takes priority.

</dd>
<dt id="olc---outdent-long-comments">-olc, --outdent-long-comments</dt>
<dd>

When -olc is set, lines which are full-line (block) comments longer than the value maximum-line-length will have their indentation removed. This is the default; use -nolc to prevent outdenting.

</dd>
<dt id="msc-n---minimum-space-to-comment-n">-msc=n, --minimum-space-to-comment=n</dt>
<dd>

Side comments look best when lined up several spaces to the right of code. Perltidy will try to keep comments at least n spaces to the right. The default is n=4 spaces.

</dd>
<dt id="fpsc-n---fixed-position-side-comment-n">-fpsc=n, --fixed-position-side-comment=n</dt>
<dd>

This parameter tells perltidy to line up side comments in column number n whenever possible. The default, n=0, will not do this.

</dd>
<dt id="iscl---ignore-side-comment-lengths">-iscl, --ignore-side-comment-lengths</dt>
<dd>

This parameter causes perltidy to ignore the length of side comments when setting line breaks. The default, -niscl, is to include the length of side comments when breaking lines to stay within the length prescribed by the -l=n maximum line length parameter. For example, the following long single line would remain intact with -l=80 and -iscl:

<pre><code> perltidy -l=80 -iscl
 $vmsfile =~ s/;[\d\-]*$//; # Clip off version number; we can use a newer version as well</code></pre>

whereas without the -iscl flag the line will be broken:

<pre><code> perltidy -l=80
 $vmsfile =~ s/;[\d\-]*$//
 ; # Clip off version number; we can use a newer version as well
 </code></pre>

</dd>
<dt id="hsc---hanging-side-comments">-hsc, --hanging-side-comments</dt>
<dd>

By default, perltidy tries to identify and align &quot;hanging side comments&quot;, which are something like this:

<pre><code> my $IGNORE = 0; # This is a side comment
 # This is a hanging side comment
 # And so is this</code></pre>

A comment is considered to be a hanging side comment if (1) it immediately follows a line with a side comment, or another hanging side comment, and (2) there is some leading whitespace on the line. To deactivate this feature, use -nhsc or --nohanging-side-comments. If block comments are preceded by a blank line, or have no leading whitespace, they will not be mistaken as hanging side comments.

</dd>
<dt id="Closing-Side-Comments">Closing Side Comments</dt>
<dd>

A closing side comment is a special comment which perltidy can automatically create and place after the closing brace of a code block. They can be useful for code maintenance and debugging. The command -csc (or --closing-side-comments) adds or updates closing side comments. For example, here is a small code snippet

<pre><code> sub message {
 if ( !defined( $_[0] ) ) {
 print(&quot;Hello, World\n&quot;);
 }
 else {
 print( $_[0], &quot;\n&quot; );
 }
 }</code></pre>

And here is the result of processing with <code>perltidy -csc</code>:

<pre><code> sub message {
 if ( !defined( $_[0] ) ) {
 print(&quot;Hello, World\n&quot;);
 }
 else {
 print( $_[0], &quot;\n&quot; );
 }
 } ## end sub message</code></pre>

A closing side comment was added for <code>sub message</code> in this case, but not for the <code>if</code> and <code>else</code> blocks, because they were below the 6 line cutoff limit for adding closing side comments. This limit may be changed with the -csci command, described below.

The command -dcsc (or --delete-closing-side-comments) reverses this process and removes these comments.

Several commands are available to modify the behavior of these two basic commands, -csc and -dcsc:

<dl>

<dt id="csci-n-or---closing-side-comment-interval-n">-csci=n, or --closing-side-comment-interval=n</dt>
<dd>

where <code>n</code> is the minimum number of lines that a block must have in order for a closing side comment to be added. The default value is <code>n=6</code>. To illustrate:

<pre><code> # perltidy -csci=2 -csc
 sub message {
 if ( !defined( $_[0] ) ) {
 print(&quot;Hello, World\n&quot;);
 } ## end if ( !defined( $_[0] ))
 else {
 print( $_[0], &quot;\n&quot; );
 } ## end else [ if ( !defined( $_[0] ))
 } ## end sub message</code></pre>

Now the <code>if</code> and <code>else</code> blocks are commented. However, now this has become very cluttered.

</dd>
<dt id="cscp-string-or---closing-side-comment-prefix-string">-cscp=string, or --closing-side-comment-prefix=string</dt>
<dd>

where string is the prefix used before the name of the block type. The default prefix, shown above, is <code>## end</code>. This string will be added to closing side comments, and it will also be used to recognize them in order to update, delete, and format them. Any comment identified as a closing side comment will be placed just a single space to the right of its closing brace.

</dd>
<dt id="cscl-string-or---closing-side-comment-list">-cscl=string, or --closing-side-comment-list</dt>
<dd>

where <code>string</code> is a list of block types to be tagged with closing side comments. By default, all code block types preceded by a keyword or label (such as <code>if</code>, <code>sub</code>, and so on) will be tagged. The -cscl command changes the default list to be any selected block types; see <a href="#Specifying-Block-Types">&quot;Specifying Block Types&quot;</a>. For example, the following command requests that only <code>sub</code>&#39;s, labels, <code>BEGIN</code>, and <code>END</code> blocks be affected by any -csc or -dcsc operation:

<pre><code> -cscl=&quot;sub : BEGIN END&quot;</code></pre>

</dd>
<dt id="csct-n-or---closing-side-comment-maximum-text-n">-csct=n, or --closing-side-comment-maximum-text=n</dt>
<dd>

The text appended to certain block types, such as an <code>if</code> block, is whatever lies between the keyword introducing the block, such as <code>if</code>, and the opening brace. Since this might be too much text for a side comment, there needs to be a limit, and that is the purpose of this parameter. The default value is <code>n=20</code>, meaning that no additional tokens will be appended to this text after its length reaches 20 characters. Omitted text is indicated with <code>...</code>. (Tokens, including sub names, are never truncated, however, so actual lengths may exceed this). To illustrate, in the above example, the appended text of the first block is <code> ( !defined( $_[0] )...</code>. The existing limit of <code>n=20</code> caused this text to be truncated, as indicated by the <code>...</code>. See the next flag for additional control of the abbreviated text.

</dd>
<dt id="cscb-or---closing-side-comments-balanced">-cscb, or --closing-side-comments-balanced</dt>
<dd>

As discussed in the previous item, when the closing-side-comment-maximum-text limit is exceeded the comment text must be truncated. Older versions of perltidy terminated with three dots, and this can still be achieved with -ncscb:

<pre><code> perltidy -csc -ncscb
 } ## end foreach my $foo (sort { $b cmp $a ...</code></pre>

However this causes a problem with editors which cannot recognize comments or are not configured to do so because they cannot &quot;bounce&quot; around in the text correctly. The -cscb flag has been added to help them by appending appropriate balancing structure:

<pre><code> perltidy -csc -cscb
 } ## end foreach my $foo (sort { $b cmp $a ... })</code></pre>

The default is -cscb.

</dd>
<dt id="csce-n-or---closing-side-comment-else-flag-n">-csce=n, or --closing-side-comment-else-flag=n</dt>
<dd>

The default, n=0, places the text of the opening <code>if</code> statement after any terminal <code>else</code>.

If n=2 is used, then each <code>elsif</code> is also given the text of the opening <code>if</code> statement. Also, an <code>else</code> will include the text of a preceding <code>elsif</code> statement. Note that this may result some long closing side comments.

If n=1 is used, the results will be the same as n=2 whenever the resulting line length is less than the maximum allowed.

</dd>
<dt id="cscb-or---closing-side-comments-balanced1">-cscb, or --closing-side-comments-balanced</dt>
<dd>

When using closing-side-comments, and the closing-side-comment-maximum-text limit is exceeded, then the comment text must be abbreviated. It is terminated with three dots if the -cscb flag is negated:

<pre><code> perltidy -csc -ncscb
 } ## end foreach my $foo (sort { $b cmp $a ...</code></pre>

This causes a problem with older editors which do not recognize comments because they cannot &quot;bounce&quot; around in the text correctly. The -cscb flag tries to help them by appending appropriate terminal balancing structures:

<pre><code> perltidy -csc -cscb
 } ## end foreach my $foo (sort { $b cmp $a ... })</code></pre>

The default is -cscb.

</dd>
<dt id="cscw-or---closing-side-comment-warnings">-cscw, or --closing-side-comment-warnings</dt>
<dd>

This parameter is intended to help make the initial transition to the use of closing side comments. It causes two things to happen if a closing side comment replaces an existing, different closing side comment: first, an error message will be issued, and second, the original side comment will be placed alone on a new specially marked comment line for later attention.

The intent is to avoid clobbering existing hand-written side comments which happen to match the pattern of closing side comments. This flag should only be needed on the first run with -csc.

</dd>
</dl>

Important Notes on Closing Side Comments:

<ul>

<li>Closing side comments are only placed on lines terminated with a closing brace. Certain closing styles, such as the use of cuddled elses (-ce), preclude the generation of some closing side comments.

</li>
<li>Please note that adding or deleting of closing side comments takes place only through the commands -csc or -dcsc. The other commands, if used, merely modify the behavior of these two commands.

</li>
<li>It is recommended that the -cscw flag be used along with -csc on the first use of perltidy on a given file. This will prevent loss of any existing side comment data which happens to have the csc prefix.

</li>
<li>Once you use -csc, you should continue to use it so that any closing side comments remain correct as code changes. Otherwise, these comments will become incorrect as the code is updated.

</li>
<li>If you edit the closing side comments generated by perltidy, you must also change the prefix to be different from the closing side comment prefix. Otherwise, your edits will be lost when you rerun perltidy with -csc. For example, you could simply change <code>## end</code> to be <code>## End</code>, since the test is case sensitive. You may also want to use the -ssc flag to keep these modified closing side comments spaced the same as actual closing side comments.

</li>
<li>Temporarily generating closing side comments is a useful technique for exploring and/or debugging a perl script, especially one written by someone else. You can always remove them with -dcsc.

</li>
</ul>

</dd>
<dt id="Static-Block-Comments">Static Block Comments</dt>
<dd>

Static block comments are block comments with a special leading pattern, <code>##</code> by default, which will be treated slightly differently from other block comments. They effectively behave as if they had glue along their left and top edges, because they stick to the left edge and previous line when there is no blank spaces in those places. This option is particularly useful for controlling how commented code is displayed.

<dl>

<dt id="sbc---static-block-comments">-sbc, --static-block-comments</dt>
<dd>

When -sbc is used, a block comment with a special leading pattern, <code>##</code> by default, will be treated specially.

Comments so identified are treated as follows:

<ul>

<li>If there is no leading space on the line, then the comment will not be indented, and otherwise it may be,

</li>
<li>no new blank line will be inserted before such a comment, and

</li>
<li>such a comment will never become a hanging side comment.

</li>
</ul>

For example, assuming <code>@month_of_year</code> is left-adjusted:

<pre><code> @month_of_year = ( # -sbc (default)
 &#39;Jan&#39;, &#39;Feb&#39;, &#39;Mar&#39;, &#39;Apr&#39;, &#39;May&#39;, &#39;Jun&#39;, &#39;Jul&#39;, &#39;Aug&#39;, &#39;Sep&#39;, &#39;Oct&#39;,
 ## &#39;Dec&#39;, &#39;Nov&#39;
 &#39;Nov&#39;, &#39;Dec&#39;);</code></pre>

Without this convention, the above code would become

<pre><code> @month_of_year = ( # -nsbc
 &#39;Jan&#39;, &#39;Feb&#39;, &#39;Mar&#39;, &#39;Apr&#39;, &#39;May&#39;, &#39;Jun&#39;, &#39;Jul&#39;, &#39;Aug&#39;, &#39;Sep&#39;, &#39;Oct&#39;,
 
 ## &#39;Dec&#39;, &#39;Nov&#39;
 &#39;Nov&#39;, &#39;Dec&#39;
 );</code></pre>

which is not as clear. The default is to use -sbc. This may be deactivated with -nsbc.

</dd>
<dt id="sbcp-string---static-block-comment-prefix-string">-sbcp=string, --static-block-comment-prefix=string</dt>
<dd>

This parameter defines the prefix used to identify static block comments when the -sbc parameter is set. The default prefix is <code>##</code>, corresponding to <code>-sbcp=##</code>. The prefix is actually part of a perl pattern used to match lines and it must either begin with <code>#</code> or <code>^#</code>. In the first case a prefix ^\s* will be added to match any leading whitespace, while in the second case the pattern will match only comments with no leading whitespace. For example, to identify all comments as static block comments, one would use <code>-sbcp=#</code>. To identify all left-adjusted comments as static block comments, use <code>-sbcp=&#39;^#&#39;</code>.

Please note that -sbcp merely defines the pattern used to identify static block comments; it will not be used unless the switch -sbc is set. Also, please be aware that since this string is used in a perl regular expression which identifies these comments, it must enable a valid regular expression to be formed.

A pattern which can be useful is:

This pattern requires a static block comment to have at least one character which is neither a # nor a space. It allows a line containing only &#39;#&#39; characters to be rejected as a static block comment. Such lines are often used at the start and end of header information in subroutines and should not be separated from the intervening comments, which typically begin with just a single &#39;#&#39;.

</dd>
<dt id="osbc---outdent-static-block-comments">-osbc, --outdent-static-block-comments</dt>
<dd>

The command -osbc will cause static block comments to be outdented by 2 spaces (or whatever -ci=n has been set to), if possible.

</dd>
</dl>

</dd>
<dt id="Static-Side-Comments">Static Side Comments</dt>
<dd>

Static side comments are side comments with a special leading pattern. This option can be useful for controlling how commented code is displayed when it is a side comment.

<dl>

<dt id="ssc---static-side-comments">-ssc, --static-side-comments</dt>
<dd>

When -ssc is used, a side comment with a static leading pattern, which is <code>##</code> by default, will be spaced only a single space from previous character, and it will not be vertically aligned with other side comments.

The default is -nssc.

</dd>
<dt id="sscp-string---static-side-comment-prefix-string">-sscp=string, --static-side-comment-prefix=string</dt>
<dd>

This parameter defines the prefix used to identify static side comments when the -ssc parameter is set. The default prefix is <code>##</code>, corresponding to <code>-sscp=##</code>.

Please note that -sscp merely defines the pattern used to identify static side comments; it will not be used unless the switch -ssc is set. Also, note that this string is used in a perl regular expression which identifies these comments, so it must enable a valid regular expression to be formed.

</dd>
</dl>

<h2 id="Skipping-Selected-Sections-of-Code">Skipping Selected Sections of Code</h2>

Selected lines of code may be passed verbatim to the output without any formatting. This feature is enabled by default but can be disabled with the --noformat-skipping or -nfs flag. It should be used sparingly to avoid littering code with markers, but it might be helpful for working around occasional problems. For example it might be useful for keeping the indentation of old commented code unchanged, keeping indentation of long blocks of aligned comments unchanged, keeping certain list formatting unchanged, or working around a glitch in perltidy.

<dl>

<dt id="fs---format-skipping">-fs, --format-skipping</dt>
<dd>

This flag, which is enabled by default, causes any code between special beginning and ending comment markers to be passed to the output without formatting. The default beginning marker is #&lt;&lt;&lt; and the default ending marker is #&gt;&gt;&gt; but they may be changed (see next items below). Additional text may appear on these special comment lines provided that it is separated from the marker by at least one space. For example

<pre><code> #&lt;&lt;&lt; do not let perltidy touch this
 my @list = (1,
 1, 1,
 1, 2, 1,
 1, 3, 3, 1,
 1, 4, 6, 4, 1,);
 #&gt;&gt;&gt;</code></pre>

Format skipping begins when a format skipping comment is seen and continues until either a format-skipping end pattern is found or until the end of file.

The comment markers may be placed at any location that a block comment may appear. If they do not appear to be working, use the -log flag and examine the .LOG file. Use -nfs to disable this feature.

This method works for any code. For the specific case of a comma-separated list of values, as in this example, another possibility is to insert a blank or comment somewhere between the opening and closing parens. See the section <a href="#Controlling-List-Formatting">&quot;Controlling List Formatting&quot;</a>.

</dd>
<dt id="fsb-string---format-skipping-begin-string">-fsb=string, --format-skipping-begin=string</dt>
<dd>

The -fsb=string parameter may be used to change the beginning marker for format skipping. The default is equivalent to -fsb=&#39;#&lt;&lt;&lt;&#39;. The string that you enter must begin with a # and should be in quotes as necessary to get past the command shell of your system. It is actually the leading text of a pattern that is constructed by appending a &#39;\s&#39;, so you must also include backslashes for characters to be taken literally rather than as patterns.

Some examples show how example strings become patterns:

<pre><code> -fsb=&#39;#\{\{\{&#39; becomes /^#\{\{\{\s/ which matches #{{{ but not #{{{{
 -fsb=&#39;#\*\*&#39; becomes /^#\*\*\s/ which matches #** but not #***
 -fsb=&#39;#\*{2,}&#39; becomes /^#\*{2,}\s/ which matches #** and #***** </code></pre>

</dd>
<dt id="fse-string---format-skipping-end-string">-fse=string, --format-skipping-end=string</dt>
<dd>

The -fse=string is the corresponding parameter used to change the ending marker for format skipping. The default is equivalent to -fse=&#39;#&lt;&lt;&lt;&#39;.

The beginning and ending strings may be the same, but it is preferable to make them different for clarity.

</dd>
</dl>

<h2 id="Line-Break-Control">Line Break Control</h2>

The parameters in this section control breaks after non-blank lines of code. Blank lines are controlled separately by parameters in the section <a href="#Blank-Line-Control">&quot;Blank Line Control&quot;</a>.

<dl>

<dt id="fnl---freeze-newlines">-fnl, --freeze-newlines</dt>
<dd>

If you do not want any changes to the line breaks within lines of code in your script, set -fnl, and they will remain fixed, and the rest of the commands in this section and sections <a href="#Controlling-List-Formatting">&quot;Controlling List Formatting&quot;</a>, <a href="#Retaining-or-Ignoring-Existing-Line-Breaks">&quot;Retaining or Ignoring Existing Line Breaks&quot;</a>. You may want to use -noll with this.

Note: If you also want to keep your blank lines exactly as they are, you can use the -fbl flag which is described in the section <a href="#Blank-Line-Control">&quot;Blank Line Control&quot;</a>.

</dd>
<dt id="ce---cuddled-else">-ce, --cuddled-else</dt>
<dd>

Enable the &quot;cuddled else&quot; style, in which <code>else</code> and <code>elsif</code> are follow immediately after the curly brace closing the previous block. The default is not to use cuddled elses, and is indicated with the flag -nce or --nocuddled-else. Here is a comparison of the alternatives:

<pre><code> # -ce
 if ($task) {
 yyy();
 } else { 
 zzz();
 }

# -nce (default)
 if ($task) {
 yyy();
 }
 else { 
 zzz();
 }</code></pre>

In this example the keyword else is placed on the same line which begins with the preceding closing block brace and is followed by its own opening block brace on the same line. Other keywords and function names which are formatted with this &quot;cuddled&quot; style are elsif, continue, catch, finally.

Other block types can be formatted by specifying their names on a separate parameter -cbl, described in a later section.

Cuddling between a pair of code blocks requires that the closing brace of the first block start a new line. If this block is entirely on one line in the input file, it is necessary to decide if it should be broken to allow cuddling. This decision is controlled by the flag -cbo=n discussed below. The default and recommended value of -cbo=1 bases this decision on the first block in the chain. If it spans multiple lines then cuddling is made and continues along the chain, regardless of the sizes of subsequent blocks. Otherwise, short lines remain intact.

So for example, the -ce flag would not have any effect if the above snippet is rewritten as

If the first block spans multiple lines, then cuddling can be done and will continue for the subsequent blocks in the chain, as illustrated in the previous snippet.

If there are blank lines between cuddled blocks they will be eliminated. If there are comments after the closing brace where cuddling would occur then cuddling will be prevented. If this occurs, cuddling will restart later in the chain if possible.

</dd>
<dt id="cb---cuddled-blocks">-cb, --cuddled-blocks</dt>
<dd>

This flag is equivalent to -ce.

</dd>
<dt id="cbl---cuddled-block-list">-cbl, --cuddled-block-list</dt>
<dd>

The built-in default cuddled block types are else, elsif, continue, catch, finally.

Additional block types to which the -cuddled-blocks style applies can be defined by this parameter. This parameter is a character string, giving a list of block types separated by commas or spaces. For example, to cuddle code blocks of type sort, map and grep, in addition to the default types, the string could be set to

or equivalently

Note however that these particular block types are typically short so there might not be much opportunity for the cuddled format style.

Using commas avoids the need to protect spaces with quotes.

As a diagnostic check, the flag --dump-cuddled-block-list or -dcbl can be used to view the hash of values that are generated by this flag.

Finally, note that the -cbl flag by itself merely specifies which blocks are formatted with the cuddled format. It has no effect unless this formatting style is activated with -ce.

</dd>
<dt id="cblx---cuddled-block-list-exclusive">-cblx, --cuddled-block-list-exclusive</dt>
<dd>

When cuddled else formatting is selected with -ce, setting this flag causes perltidy to ignore its built-in defaults and rely exclusively on the block types specified on the -cbl flag described in the previous section. For example, to avoid using cuddled catch and finally, which among in the defaults, the following set of parameters could be used:

<pre><code> perltidy -ce -cbl=&#39;else elsif continue&#39; -cblx</code></pre>

</dd>
<dt id="cbo-n---cuddled-break-option-n">-cbo=n, --cuddled-break-option=n</dt>
<dd>

Cuddled formatting is only possible between a pair of code blocks if the closing brace of the first block starts a new line. If a block is encountered which is entirely on a single line, and cuddled formatting is selected, it is necessary to make a decision as to whether or not to &quot;break&quot; the block, meaning to cause it to span multiple lines. This parameter controls that decision. The options are:

<pre><code> cbo=0 Never force a short block to break.
 cbo=1 If the first of a pair of blocks is broken in the input file, 
 then break the second [DEFAULT].
 cbo=2 Break open all blocks for maximal cuddled formatting.</code></pre>

The default and recommended value is cbo=1. With this value, if the starting block of a chain spans multiple lines, then a cascade of breaks will occur for remaining blocks causing the entire chain to be cuddled.

The option cbo=0 can produce erratic cuddling if there are numerous one-line blocks.

The option cbo=2 produces maximal cuddling but will not allow any short blocks.

</dd>
<dt id="bl---opening-brace-on-new-line">-bl, --opening-brace-on-new-line</dt>
<dd>

Use the flag -bl to place the opening brace on a new line:

<pre><code> if ( $input_file eq &#39;-&#39; ) # -bl 
 { 
 important_function();
 }</code></pre>

This flag applies to all structural blocks, including named sub&#39;s (unless the -sbl flag is set -- see next item).

The default style, -nbl, places an opening brace on the same line as the keyword introducing it. For example,

<pre><code> if ( $input_file eq &#39;-&#39; ) { # -nbl (default)</code></pre>

</dd>
<dt id="sbl---opening-sub-brace-on-new-line">-sbl, --opening-sub-brace-on-new-line</dt>
<dd>

The flag -sbl can be used to override the value of -bl for the opening braces of named sub&#39;s. For example,

<pre><code> perltidy -sbl</code></pre>

produces this result:

<pre><code> sub message
 {
 if (!defined($_[0])) {
 print(&quot;Hello, World\n&quot;);
 }
 else {
 print($_[0], &quot;\n&quot;);
 }
 }</code></pre>

This flag is negated with -nsbl. If -sbl is not specified, the value of -bl is used.

</dd>
<dt id="asbl---opening-anonymous-sub-brace-on-new-line">-asbl, --opening-anonymous-sub-brace-on-new-line</dt>
<dd>

The flag -asbl is like the -sbl flag except that it applies to anonymous sub&#39;s instead of named subs. For example

<pre><code> perltidy -asbl</code></pre>

produces this result:

<pre><code> $a = sub
 {
 if ( !defined( $_[0] ) ) {
 print(&quot;Hello, World\n&quot;);
 }
 else {
 print( $_[0], &quot;\n&quot; );
 }
 };</code></pre>

This flag is negated with -nasbl, and the default is -nasbl.

</dd>
<dt id="bli---brace-left-and-indent">-bli, --brace-left-and-indent</dt>
<dd>

The flag -bli is the same as -bl but in addition it causes one unit of continuation indentation ( see -ci ) to be placed before an opening and closing block braces.

For example,

<pre><code> if ( $input_file eq &#39;-&#39; ) # -bli
 {
 important_function();
 }</code></pre>

By default, this extra indentation occurs for blocks of type: if, elsif, else, unless, for, foreach, sub, while, until, and also with a preceding label. The next item shows how to change this.

</dd>
<dt id="blil-s---brace-left-and-indent-list-s">-blil=s, --brace-left-and-indent-list=s</dt>
<dd>

Use this parameter to change the types of block braces for which the -bli flag applies; see <a href="#Specifying-Block-Types">&quot;Specifying Block Types&quot;</a>. For example, -blil=&#39;if elsif else&#39; would apply it to only <code>if/elsif/else</code> blocks.

</dd>
<dt id="bar---opening-brace-always-on-right">-bar, --opening-brace-always-on-right</dt>
<dd>

The default style, -nbl places the opening code block brace on a new line if it does not fit on the same line as the opening keyword, like this:

<pre><code> if ( $bigwasteofspace1 &amp;&amp; $bigwasteofspace2
 || $bigwasteofspace3 &amp;&amp; $bigwasteofspace4 )
 {
 big_waste_of_time();
 }</code></pre>

To force the opening brace to always be on the right, use the -bar flag. In this case, the above example becomes

<pre><code> if ( $bigwasteofspace1 &amp;&amp; $bigwasteofspace2
 || $bigwasteofspace3 &amp;&amp; $bigwasteofspace4 ) {
 big_waste_of_time();
 }</code></pre>

A conflict occurs if both -bl and -bar are specified.

</dd>
<dt id="otr---opening-token-right-and-related-flags">-otr, --opening-token-right and related flags</dt>
<dd>

The -otr flag is a hint that perltidy should not place a break between a comma and an opening token. For example:

<pre><code> # default formatting
 push @{ $self-&gt;{$module}{$key} },
 {
 accno =&gt; $ref-&gt;{accno},
 description =&gt; $ref-&gt;{description}
 };

# perltidy -otr
 push @{ $self-&gt;{$module}{$key} }, {
 accno =&gt; $ref-&gt;{accno},
 description =&gt; $ref-&gt;{description}
 };</code></pre>

The flag -otr is actually an abbreviation for three other flags which can be used to control parens, hash braces, and square brackets separately if desired:

<pre><code> -opr or --opening-paren-right
 -ohbr or --opening-hash-brace-right
 -osbr or --opening-square-bracket-right</code></pre>

</dd>
<dt id="bbhb-n---break-before-hash-brace-n-and-related-flags">-bbhb=n, --break-before-hash-brace=n and related flags</dt>
<dd>

When a list of items spans multiple lines, the default formatting is to place the opening brace (or other container token) at the end of the starting line, like this:

<pre><code> $romanNumerals = {
 one =&gt; &#39;I&#39;,
 two =&gt; &#39;II&#39;,
 three =&gt; &#39;III&#39;,
 four =&gt; &#39;IV&#39;,
 };</code></pre>

This flag can change the default behavior to cause a line break to be placed before the opening brace according to the value given to the integer n:

<pre><code> -bbhb=0 never break [default]
 -bbhb=1 stable: break if the input script had a break
 -bbhb=2 break if list is &#39;complex&#39; (see note below)
 -bbhb=3 always break</code></pre>

For example,

<pre><code> # perltidy -bbhb=3
 $romanNumerals =
 {
 one =&gt; &#39;I&#39;,
 two =&gt; &#39;II&#39;,
 three =&gt; &#39;III&#39;,
 four =&gt; &#39;IV&#39;,
 };</code></pre>

There are several points to note about this flag:

<ul>

<li>This parameter only applies if the opening brace is preceded by an &#39;=&#39; or &#39;=&gt;&#39;.

</li>
<li>This parameter only applies if the contents of the container looks like a list. The contents need to contain some commas or &#39;=&gt;&#39;s at the next interior level to be considered a list.

</li>
<li>For the n=2 option, a list is considered &#39;complex&#39; if it is part of a nested list structure which spans multiple lines in the input file.

</li>
<li>If multiple opening tokens have been &#39;welded&#39; together with the -wn parameter, then this parameter has no effect.

</li>
<li>The indentation of the braces will normally be one level of continuation indentation by default. This can be changed with the parameter -bbhbi=n in the next section.

</li>
<li>Similar flags for controlling parens and square brackets are given in the subsequent section.

</li>
</ul>

</dd>
<dt id="bbhbi-n---break-before-hash-brace-and-indent-n">-bbhbi=n, --break-before-hash-brace-and-indent=n</dt>
<dd>

This flag is a companion to -bbhb=n for controlling the indentation of an opening hash brace which is placed on a new line by that parameter. The indentation is as follows:

<pre><code> -bbhbi=0 one continuation level [default]
 -bbhbi=1 outdent by one continuation level
 -bbhbi=2 indent one full indentation level</code></pre>

For example:

<pre><code> # perltidy -bbhb=3 -bbhbi=1
 $romanNumerals =
 {
 one =&gt; &#39;I&#39;,
 two =&gt; &#39;II&#39;,
 three =&gt; &#39;III&#39;,
 four =&gt; &#39;IV&#39;,
 };

# perltidy -bbhb=3 -bbhbi=2
 $romanNumerals =
 {
 one =&gt; &#39;I&#39;,
 two =&gt; &#39;II&#39;,
 three =&gt; &#39;III&#39;,
 four =&gt; &#39;IV&#39;,
 };</code></pre>

Note that this parameter has no effect unless -bbhb=n is also set.

</dd>
<dt id="bbsb-n---break-before-square-bracket-n">-bbsb=n, --break-before-square-bracket=n</dt>
<dd>

This flag is similar to the flag described above, except it applies to lists contained within square brackets.

<pre><code> -bbsb=0 never break [default]
 -bbsb=1 stable: break if the input script had a break
 -bbsb=2 break if list is &#39;complex&#39; (part of nested list structure)
 -bbsb=3 always break</code></pre>

</dd>
<dt id="bbsbi-n---break-before-square-bracket-and-indent-n">-bbsbi=n, --break-before-square-bracket-and-indent=n</dt>
<dd>

This flag is a companion to -bbsb=n for controlling the indentation of an opening square bracket which is placed on a new line by that parameter. The indentation is as follows:

<pre><code> -bbsbi=0 one continuation level [default]
 -bbsbi=1 outdent by one continuation level
 -bbsbi=2 indent one full indentation level</code></pre>

</dd>
<dt id="bbp-n---break-before-paren-n">-bbp=n, --break-before-paren=n</dt>
<dd>

This flag is similar to -bbhb=n, described above, except it applies to lists contained within parens.

<pre><code> -bbp=0 never break [default]
 -bbp=1 stable: break if the input script had a break
 -bpb=2 break if list is &#39;complex&#39; (part of nested list structure)
 -bbp=3 always break</code></pre>

</dd>
<dt id="bbpi-n---break-before-paren-and-indent-n">-bbpi=n, --break-before-paren-and-indent=n</dt>
<dd>

This flag is a companion to -bbp=n for controlling the indentation of an opening paren which is placed on a new line by that parameter. The indentation is as follows:

<pre><code> -bbpi=0 one continuation level [default]
 -bbpi=1 outdent by one continuation level
 -bbpi=2 indent one full indentation level</code></pre>

</dd>
<dt id="wn---weld-nested-containers">-wn, --weld-nested-containers</dt>
<dd>

The -wn flag causes closely nested pairs of opening and closing container symbols (curly braces, brackets, or parens) to be &quot;welded&quot; together, meaning that they are treated as if combined into a single unit, with the indentation of the innermost code reduced to be as if there were just a single container symbol.

For example:

<pre><code> # default formatting
 do {
 {
 next if $x == $y; 
 }
 } until $x++ &gt; $z;

# perltidy -wn
 do { {
 next if $x == $y;
 } } until $x++ &gt; $z;</code></pre>

When this flag is set perltidy makes a preliminary pass through the file and identifies all nested pairs of containers. To qualify as a nested pair, the closing container symbols must be immediately adjacent and the opening symbols must either (1) be adjacent as in the above example, or (2) have an anonymous sub declaration following an outer opening container symbol which is not a code block brace, or (3) have an outer opening paren separated from the inner opening symbol by any single non-container symbol or something that looks like a function evaluation, as illustrated in the next examples.

Any container symbol may serve as both the inner container of one pair and as the outer container of an adjacent pair. Consequently, any number of adjacent opening or closing symbols may join together in weld. For example, here are three levels of wrapped function calls:

<pre><code> # default formatting
 my (@date_time) = Localtime(
 Date_to_Time(
 Add_Delta_DHMS(
 $year, $month, $day, $hour, $minute, $second,
 &#39;0&#39;, $offset, &#39;0&#39;, &#39;0&#39;
 )
 )
 );

# perltidy -wn
 my (@date_time) = Localtime( Date_to_Time( Add_Delta_DHMS(
 $year, $month, $day, $hour, $minute, $second,
 &#39;0&#39;, $offset, &#39;0&#39;, &#39;0&#39;
 ) ) );</code></pre>

Notice how the indentation of the inner lines are reduced by two levels in this case. This example also shows the typical result of this formatting, namely it is a sandwich consisting of an initial opening layer, a central section of any complexity forming the &quot;meat&quot; of the sandwich, and a final closing layer. This predictable structure helps keep the compacted structure readable.

The inner sandwich layer is required to be at least one line thick. If this cannot be achieved, welding does not occur. This constraint can cause formatting to take a couple of iterations to stabilize when it is first applied to a script. The -conv flag can be used to insure that the final format is achieved in a single run.

Here is an example illustrating a welded container within a welded containers:

<pre><code> # default formatting
 $x-&gt;badd(
 bmul(
 $class-&gt;new(
 abs(
 $sx * int( $xr-&gt;numify() ) &amp; $sy * int( $yr-&gt;numify() )
 )
 ),
 $m
 )
 );

# perltidy -wn
 $x-&gt;badd( bmul(
 $class-&gt;new( abs(
 $sx * int( $xr-&gt;numify() ) &amp; $sy * int( $yr-&gt;numify() )
 ) ),
 $m
 ) );</code></pre>

The welded closing tokens are by default on a separate line but this can be modified with the -vtc=n flag (described in the next section). For example, the same example adding -vtc-2 is

<pre><code> # perltidy -wn -vtc=2
 $x-&gt;badd( bmul(
 $class-&gt;new( abs(
 $sx * int( $xr-&gt;numify() ) &amp; $sy * int( $yr-&gt;numify() ) ) ),
 $m ) );</code></pre>

This format option is quite general but there are some limitations.

One limitation is that any line length limit still applies and can cause long welded sections to be broken into multiple lines.

Another limitation is that an opening symbol which delimits quoted text cannot be included in a welded pair. This is because quote delimiters are treated specially in perltidy.

Finally, the stacking of containers defined by this flag have priority over any other container stacking flags. This is because any welding is done first.

</dd>
<dt id="wnxl-s---weld-nested-exclusion-list">-wnxl=s, --weld-nested-exclusion-list</dt>
<dd>

The -wnxl=s flag provides some control over the types of containers which can be welded. The -wn flag by default is &quot;greedy&quot; in welding adjacent containers. If it welds more types of containers than desired, this flag provides a capability to reduce the amount of welding by specifying a list of things which should not be welded.

The logic in perltidy to apply this is straightforward. As each container token is being considered for joining a weld, any exclusion rules are consulted and used to reject the weld if necessary.

This list is a string with space-separated items. Each item consists of up to three pieces of information: (1) an optional positiion, (2) an optional preceding type, and (3) a container type.

The only required piece of information is a container type, which is one of &#39;(&#39;, &#39;[&#39;, &#39;{&#39; or &#39;q&#39;. The first three of these are container tokens and the last represents a quoted list. For example the string

means do NOT include square-bracets, braces, or quotes in any welds. The only unspecified container is &#39;(&#39;, so this string means that only welds involving parens will be made.

To illustrate, following welded snippet consists of a chain of three welded containers with types &#39;(&#39; &#39;[&#39; and &#39;q&#39;:

<pre><code> # perltidy -wn
 skip_symbols( [ qw(
 Perl_dump_fds
 Perl_ErrorNo
 Perl_GetVars
 PL_sys_intern
 ) ] );</code></pre>

Even though the qw term uses parens as the quote delimiter, it has a special type &#39;q&#39; here. If it appears in a weld it always appears at the end of the welded chain.

Any of the container types &#39;[&#39;, &#39;{&#39;, and &#39;(&#39; may be prefixed with a position indicator which is either &#39;^&#39;, to indicate the first token of a welded sequence, or &#39;.&#39;, to indicate an interior token of a welded sequence. (Since a quoted string &#39;q&#39; always ends a chain it does need a position indicator).

For example, if we do not want a sequence of welded containers to start with a square bracket we could use

In the above snippet, there is a square bracket but it does not start the chain, so the formatting would be unchanged if it were formatted with this restriction.

A third optional item of information which can be given is an alphanumeric letter which is used to limit the selection further depending on the type of token immediately before the container. If given, it goes just before the container symbol. The possible letters are currently &#39;k&#39;, &#39;K&#39;, &#39;f&#39;, &#39;F&#39;, &#39;w&#39;, and &#39;W&#39;, with these meanings:

<pre><code> &#39;k&#39; matches if the previous nonblank token is a perl builtin keyword (such as &#39;if&#39;, &#39;while&#39;), 
 &#39;K&#39; matches if &#39;k&#39; does not, meaning that the previous token is not a keyword.
 &#39;f&#39; matches if the previous token is a function other than a keyword.
 &#39;F&#39; matches if &#39;f&#39; does not.
 &#39;w&#39; matches if either &#39;k&#39; or &#39;f&#39; match.
 &#39;W&#39; matches if &#39;w&#39; does not.</code></pre>

For example, compare

<pre><code> # perltidy -wn 
 if ( defined( $_Cgi_Query{
 $Config{&#39;methods&#39;}{&#39;authentication&#39;}{&#39;remote&#39;}{&#39;cgi&#39;}{&#39;username&#39;}
 } ) )</code></pre>

with

<pre><code> # perltidy -wn -wnxl=&#39;^K( {&#39;
 if ( defined(
 $_Cgi_Query{ $Config{&#39;methods&#39;}{&#39;authentication&#39;}{&#39;remote&#39;}{&#39;cgi&#39;}
 {&#39;username&#39;} }
 ) )</code></pre>

The first case does maximum welding. In the second case the leading paren is retained by the rule (it would have been rejected if preceded by a non-keyword) but the curly brace is rejected by the rule.

Here are some additional example strings and their meanings:

<pre><code> &#39;^(&#39; - the weld must not start with a paren
 &#39;.(&#39; - the second and later tokens may not be parens
 &#39;(&#39; - no parens in a weld
 &#39;^K(&#39; - exclude a leading paren preceded by a non-keyword
 &#39;.k(&#39; - exclude a secondary paren preceded by a keyword
 &#39;[ {&#39; - exclude all brackets and braces</code></pre>

</dd>
<dt id="Vertical-tightness-of-non-block-curly-braces-parentheses-and-square-brackets">Vertical tightness of non-block curly braces, parentheses, and square brackets.</dt>
<dd>

These parameters control what shall be called vertical tightness. Here are the main points:

<ul>

<li>Opening tokens (except for block braces) are controlled by -vt=n, or --vertical-tightness=n, where

<pre><code> -vt=0 always break a line after opening token (default). 
 -vt=1 do not break unless this would produce more than one 
 step in indentation in a line.
 -vt=2 never break a line after opening token</code></pre>

</li>
<li>You must also use the -lp flag when you use the -vt flag; the reason is explained below.

</li>
<li>Closing tokens (except for block braces) are controlled by -vtc=n, or --vertical-tightness-closing=n, where

<pre><code> -vtc=0 always break a line before a closing token (default), 
 -vtc=1 do not break before a closing token which is followed 
 by a semicolon or another closing token, and is not in 
 a list environment.
 -vtc=2 never break before a closing token.</code></pre>

The rules for -vtc=1 are designed to maintain a reasonable balance between tightness and readability in complex lists.

</li>
<li>Different controls may be applied to different token types, and it is also possible to control block braces; see below.

</li>
<li>Finally, please note that these vertical tightness flags are merely hints to the formatter, and it cannot always follow them. Things which make it difficult or impossible include comments, blank lines, blocks of code within a list, and possibly the lack of the -lp parameter. Also, these flags may be ignored for very small lists (2 or 3 lines in length).

</li>
</ul>

Here are some examples:

<pre><code> # perltidy -lp -vt=0 -vtc=0
 %romanNumerals = (
 one =&gt; &#39;I&#39;,
 two =&gt; &#39;II&#39;,
 three =&gt; &#39;III&#39;,
 four =&gt; &#39;IV&#39;,
 );

# perltidy -lp -vt=1 -vtc=0
    %romanNumerals = ( one   =&gt; &#39;I&#39;,
                       two   =&gt; &#39;II&#39;,
                       three =&gt; &#39;III&#39;,
                       four  =&gt; &#39;IV&#39;,
    );

# perltidy -lp -vt=1 -vtc=1
 %romanNumerals = ( one =&gt; &#39;I&#39;,
 two =&gt; &#39;II&#39;,
 three =&gt; &#39;III&#39;,
 four =&gt; &#39;IV&#39;, );</code></pre>

The difference between -vt=1 and -vt=2 is shown here:

<pre><code> # perltidy -lp -vt=1 
 $init-&gt;add(
 mysprintf( &quot;(void)find_threadsv(%s);&quot;,
 cstring( $threadsv_names[ $op-&gt;targ ] )
 )
 );

# perltidy -lp -vt=2 
 $init-&gt;add( mysprintf( &quot;(void)find_threadsv(%s);&quot;,
 cstring( $threadsv_names[ $op-&gt;targ ] )
 )
 );</code></pre>

With -vt=1, the line ending in <code>add(</code> does not combine with the next line because the next line is not balanced. This can help with readability, but -vt=2 can be used to ignore this rule.

The tightest, and least readable, code is produced with both <code>-vt=2</code> and <code>-vtc=2</code>:

<pre><code> # perltidy -lp -vt=2 -vtc=2
 $init-&gt;add( mysprintf( &quot;(void)find_threadsv(%s);&quot;,
 cstring( $threadsv_names[ $op-&gt;targ ] ) ) );</code></pre>

Notice how the code in all of these examples collapses vertically as -vt increases, but the indentation remains unchanged. This is because perltidy implements the -vt parameter by first formatting as if -vt=0, and then simply overwriting one output line on top of the next, if possible, to achieve the desired vertical tightness. The -lp indentation style has been designed to allow this vertical collapse to occur, which is why it is required for the -vt parameter.

The -vt=n and -vtc=n parameters apply to each type of container token. If desired, vertical tightness controls can be applied independently to each of the closing container token types.

The parameters for controlling parentheses are -pvt=n or --paren-vertical-tightness=n, and -pcvt=n or --paren-vertical-tightness-closing=n.

Likewise, the parameters for square brackets are -sbvt=n or --square-bracket-vertical-tightness=n, and -sbcvt=n or --square-bracket-vertical-tightness-closing=n.

Finally, the parameters for controlling non-code block braces are -bvt=n or --brace-vertical-tightness=n, and -bcvt=n or --brace-vertical-tightness-closing=n.

In fact, the parameter -vt=n is actually just an abbreviation for -pvt=n -bvt=n sbvt=n, and likewise -vtc=n is an abbreviation for -pvtc=n -bvtc=n sbvtc=n.

</dd>
<dt id="bbvt-n-or---block-brace-vertical-tightness-n">-bbvt=n or --block-brace-vertical-tightness=n</dt>
<dd>

The -bbvt=n flag is just like the -vt=n flag but applies to opening code block braces.

<pre><code> -bbvt=0 break after opening block brace (default). 
 -bbvt=1 do not break unless this would produce more than one 
 step in indentation in a line.
 -bbvt=2 do not break after opening block brace.</code></pre>

It is necessary to also use either -bl or -bli for this to work, because, as with other vertical tightness controls, it is implemented by simply overwriting a line ending with an opening block brace with the subsequent line. For example:

<pre><code> # perltidy -bli -bbvt=0
 if ( open( FILE, &quot;&lt; $File&quot; ) )
 {
 while ( $File = &lt;FILE&gt; )
 {
 $In .= $File;
 $count++;
 }
 close(FILE);
 }

# perltidy -bli -bbvt=1
 if ( open( FILE, &quot;&lt; $File&quot; ) )
 { while ( $File = &lt;FILE&gt; )
 { $In .= $File;
 $count++;
 }
 close(FILE);
 }</code></pre>

By default this applies to blocks associated with keywords if, elsif, else, unless, for, foreach, sub, while, until, and also with a preceding label. This can be changed with the parameter -bbvtl=string, or --block-brace-vertical-tightness-list=string, where string is a space-separated list of block types. For more information on the possible values of this string, see <a href="#Specifying-Block-Types">&quot;Specifying Block Types&quot;</a>

For example, if we want to just apply this style to <code>if</code>, <code>elsif</code>, and <code>else</code> blocks, we could use <code>perltidy -bli -bbvt=1 -bbvtl=&#39;if elsif else&#39;</code>.

There is no vertical tightness control for closing block braces; with one exception they will be placed on separate lines. The exception is that a cascade of closing block braces may be stacked on a single line. See -scbb.

</dd>
<dt id="sot---stack-opening-tokens-and-related-flags">-sot, --stack-opening-tokens and related flags</dt>
<dd>

The -sot flag tells perltidy to &quot;stack&quot; opening tokens when possible to avoid lines with isolated opening tokens.

For example:

<pre><code> # default
 $opt_c = Text::CSV_XS-&gt;new(
 {
 binary =&gt; 1,
 sep_char =&gt; $opt_c,
 always_quote =&gt; 1,
 }
 );

# -sot
 $opt_c = Text::CSV_XS-&gt;new( {
 binary =&gt; 1,
 sep_char =&gt; $opt_c,
 always_quote =&gt; 1,
 }
 );</code></pre>

For detailed control of individual closing tokens the following controls can be used:

<pre><code> -sop or --stack-opening-paren
 -sohb or --stack-opening-hash-brace
 -sosb or --stack-opening-square-bracket
 -sobb or --stack-opening-block-brace</code></pre>

The flag -sot is an abbreviation for -sop -sohb -sosb.

The flag -sobb is an abbreviation for -bbvt=2 -bbvtl=&#39;*&#39;. This will case a cascade of opening block braces to appear on a single line, although this an uncommon occurrence except in test scripts.

</dd>
<dt id="sct---stack-closing-tokens-and-related-flags">-sct, --stack-closing-tokens and related flags</dt>
<dd>

The -sct flag tells perltidy to &quot;stack&quot; closing tokens when possible to avoid lines with isolated closing tokens.

For example:

<pre><code> # default
 $opt_c = Text::CSV_XS-&gt;new(
 {
 binary =&gt; 1,
 sep_char =&gt; $opt_c,
 always_quote =&gt; 1,
 }
 );

# -sct
 $opt_c = Text::CSV_XS-&gt;new(
 {
 binary =&gt; 1,
 sep_char =&gt; $opt_c,
 always_quote =&gt; 1,
 } );</code></pre>

The -sct flag is somewhat similar to the -vtc flags, and in some cases it can give a similar result. The difference is that the -vtc flags try to avoid lines with leading opening tokens by &quot;hiding&quot; them at the end of a previous line, whereas the -sct flag merely tries to reduce the number of lines with isolated closing tokens by stacking them but does not try to hide them. For example:

<pre><code> # -vtc=2
 $opt_c = Text::CSV_XS-&gt;new(
 {
 binary =&gt; 1,
 sep_char =&gt; $opt_c,
 always_quote =&gt; 1, } );</code></pre>

For detailed control of the stacking of individual closing tokens the following controls can be used:

<pre><code> -scp or --stack-closing-paren
 -schb or --stack-closing-hash-brace
 -scsb or --stack-closing-square-bracket
 -scbb or --stack-closing-block-brace</code></pre>

The flag -sct is an abbreviation for stacking the non-block closing tokens, -scp -schb -scsb.

Stacking of closing block braces, -scbb, causes a cascade of isolated closing block braces to be combined into a single line as in the following example:

<pre><code> # -scbb:
 for $w1 (@w1) {
 for $w2 (@w2) {
 for $w3 (@w3) {
 for $w4 (@w4) {
 push( @lines, &quot;$w1 $w2 $w3 $w4\n&quot; );
 } } } }</code></pre>

To simplify input even further for the case in which both opening and closing non-block containers are stacked, the flag -sac or --stack-all-containers is an abbreviation for -sot -sot.

</dd>
<dt id="dnl---delete-old-newlines">-dnl, --delete-old-newlines</dt>
<dd>

By default, perltidy first deletes all old line break locations, and then it looks for good break points to match the desired line length. Use -ndnl or --nodelete-old-newlines to force perltidy to retain all old line break points.

</dd>
<dt id="anl---add-newlines">-anl, --add-newlines</dt>
<dd>

By default, perltidy will add line breaks when necessary to create continuations of long lines and to improve the script appearance. Use -nanl or --noadd-newlines to prevent any new line breaks.

This flag does not prevent perltidy from eliminating existing line breaks; see --freeze-newlines to completely prevent changes to line break points.

</dd>
<dt id="Controlling-whether-perltidy-breaks-before-or-after-operators">Controlling whether perltidy breaks before or after operators</dt>
<dd>

Four command line parameters provide some control over whether a line break should be before or after specific token types. Two parameters give detailed control:

-wba=s or --want-break-after=s, and

-wbb=s or --want-break-before=s.

These parameters are each followed by a quoted string, s, containing a list of token types (separated only by spaces). No more than one of each of these parameters should be specified, because repeating a command-line parameter always overwrites the previous one before perltidy ever sees it.

By default, perltidy breaks after these token types: % + - * / x != == &gt;= &lt;= =~ !~ &lt; &gt; | &amp; = **= += *= &amp;= &lt;&lt;= &amp;&amp;= -= /= |= &gt;&gt;= ||= //= .= %= ^= x=

And perltidy breaks before these token types by default: . &lt;&lt; &gt;&gt; -&gt; &amp;&amp; || //

To illustrate, to cause a break after a concatenation operator, <code>&#39;.&#39;</code>, rather than before it, the command line would be

As another example, the following command would cause a break before math operators <code>&#39;+&#39;</code>, <code>&#39;-&#39;</code>, <code>&#39;/&#39;</code>, and <code>&#39;*&#39;</code>:

These commands should work well for most of the token types that perltidy uses (use --dump-token-types for a list). Also try the -D flag on a short snippet of code and look at the .DEBUG file to see the tokenization. However, for a few token types there may be conflicts with hardwired logic which cause unexpected results. One example is curly braces, which should be controlled with the parameter bl provided for that purpose.

WARNING Be sure to put these tokens in quotes to avoid having them misinterpreted by your command shell.

Two additional parameters are available which, though they provide no further capability, can simplify input are:

-baao or --break-after-all-operators,

-bbao or --break-before-all-operators.

The -baao sets the default to be to break after all of the following operators:

and the -bbao flag sets the default to break before all of these operators. These can be used to define an initial break preference which can be fine-tuned with the -wba and -wbb flags. For example, to break before all operators except an = one could use --bbao -wba=&#39;=&#39; rather than listing every single perl operator except = on a -wbb flag.

</dd>
</dl>

<h2 id="Controlling-List-Formatting">Controlling List Formatting</h2>

Perltidy attempts to format lists of comma-separated values in tables which look good. Its default algorithms usually work well, but sometimes they don&#39;t. In this case, there are several methods available to control list formatting.

A very simple way to prevent perltidy from changing the line breaks within a comma-separated list of values is to insert a blank line, comment, or side-comment anywhere between the opening and closing parens (or braces or brackets). This causes perltidy to skip over its list formatting logic. (The reason is that any of these items put a constraint on line breaks, and perltidy needs complete control over line breaks within a container to adjust a list layout). For example, let us consider

The default formatting, which allows a maximum line length of 80, will flatten this down to one line:

<pre><code> # perltidy (default)
 my @list = ( 1, 1, 1, 1, 2, 1, 1, 3, 3, 1, 1, 4, 6, 4, 1, );</code></pre>

This formatting loses important information. If we place a side comment on one of the lines, for example, we get the following result with with default formatting parameters:

<pre><code> my @list = (
 1, # a side comment, comment, or blank keeps list intact
 1, 1,
 1, 2, 1,
 1, 3, 3, 1,
 1, 4, 6, 4, 1,
 );</code></pre>

We could achieve the same result with a blank line or full comment anywhere between the opening and closing parens.

For another possibility see the -fs flag in <a href="#Skipping-Selected-Sections-of-Code">&quot;Skipping Selected Sections of Code&quot;</a>.

<dl>

<dt id="boc---break-at-old-comma-breakpoints">-boc, --break-at-old-comma-breakpoints</dt>
<dd>

The -boc flag is another way to prevent comma-separated lists from being reformatted. Using -boc on the above example, plus additional flags to retain the original style, yields

<pre><code> # perltidy -boc -lp -pt=2 -vt=1 -vtc=1
 my @list = (1,
 1, 1,
 1, 2, 1,
 1, 3, 3, 1,
 1, 4, 6, 4, 1,);</code></pre>

A disadvantage of this flag is that all tables in the file must already be nicely formatted.

</dd>
<dt id="mft-n---maximum-fields-per-table-n">-mft=n, --maximum-fields-per-table=n</dt>
<dd>

If the computed number of fields for any table exceeds n, then it will be reduced to n. The default value for n is a large number, 40. While this value should probably be left unchanged as a general rule, it might be used on a small section of code to force a list to have a particular number of fields per line, and then either the -boc flag could be used to retain this formatting, or a single comment could be introduced somewhere to freeze the formatting in future applications of perltidy.

<pre><code> # perltidy -mft=2
 @month_of_year = ( 
 &#39;Jan&#39;, &#39;Feb&#39;,
 &#39;Mar&#39;, &#39;Apr&#39;,
 &#39;May&#39;, &#39;Jun&#39;,
 &#39;Jul&#39;, &#39;Aug&#39;,
 &#39;Sep&#39;, &#39;Oct&#39;,
 &#39;Nov&#39;, &#39;Dec&#39;
 );</code></pre>

</dd>
<dt id="cab-n---comma-arrow-breakpoints-n">-cab=n, --comma-arrow-breakpoints=n</dt>
<dd>

A comma which follows a comma arrow, &#39;=&gt;&#39;, is given special consideration. In a long list, it is common to break at all such commas. This parameter can be used to control how perltidy breaks at these commas. (However, it will have no effect if old comma breaks are being forced because -boc is used). The possible values of n are:

<pre><code> n=0 break at all commas after =&gt; 
 n=1 stable: break at all commas after =&gt; if container is open,
 EXCEPT FOR one-line containers
 n=2 break at all commas after =&gt;, BUT try to form the maximum
 maximum one-line container lengths
 n=3 do not treat commas after =&gt; specially at all 
 n=4 break everything: like n=0 but ALSO break a short container with
 a =&gt; not followed by a comma when -vt=0 is used
 n=5 stable: like n=1 but ALSO break at open one-line containers when
 -vt=0 is used (default)</code></pre>

For example, given the following single line, perltidy by default will not add any line breaks because it would break the existing one-line container:

<pre><code> bless { B =&gt; $B, Root =&gt; $Root } =&gt; $package;</code></pre>

Using -cab=0 will force a break after each comma-arrow item:

<pre><code> # perltidy -cab=0:
 bless {
 B =&gt; $B,
 Root =&gt; $Root
 } =&gt; $package;</code></pre>

If perltidy is subsequently run with this container broken, then by default it will break after each &#39;=&gt;&#39; because the container is now broken. To reform a one-line container, the parameter -cab=2 could be used.

The flag -cab=3 can be used to prevent these commas from being treated specially. In this case, an item such as &quot;01&quot; =&gt; 31 is treated as a single item in a table. The number of fields in this table will be determined by the same rules that are used for any other table. Here is an example.

<pre><code> # perltidy -cab=3
 my %last_day = (
 &quot;01&quot; =&gt; 31, &quot;02&quot; =&gt; 29, &quot;03&quot; =&gt; 31, &quot;04&quot; =&gt; 30,
 &quot;05&quot; =&gt; 31, &quot;06&quot; =&gt; 30, &quot;07&quot; =&gt; 31, &quot;08&quot; =&gt; 31,
 &quot;09&quot; =&gt; 30, &quot;10&quot; =&gt; 31, &quot;11&quot; =&gt; 30, &quot;12&quot; =&gt; 31
 );</code></pre>

</dd>
</dl>

<h2 id="Retaining-or-Ignoring-Existing-Line-Breaks">Retaining or Ignoring Existing Line Breaks</h2>

Several additional parameters are available for controlling the extent to which line breaks in the input script influence the output script. In most cases, the default parameter values are set so that, if a choice is possible, the output style follows the input style. For example, if a short logical container is broken in the input script, then the default behavior is for it to remain broken in the output script.

Most of the parameters in this section would only be required for a one-time conversion of a script from short container lengths to longer container lengths. The opposite effect, of converting long container lengths to shorter lengths, can be obtained by temporarily using a short maximum line length.

<dl>

<dt id="bol---break-at-old-logical-breakpoints">-bol, --break-at-old-logical-breakpoints</dt>
<dd>

By default, if a logical expression is broken at a <code>&amp;&amp;</code>, <code>||</code>, <code>and</code>, or <code>or</code>, then the container will remain broken. Also, breaks at internal keywords <code>if</code> and <code>unless</code> will normally be retained. To prevent this, and thus form longer lines, use -nbol.

Please note that this flag does not duplicate old logical breakpoints. They are merely used as a hint with this flag that a statement should remain broken. Without this flag, perltidy will normally try to combine relatively short expressions into a single line.

For example, given this snippet:

<pre><code> return unless $cmd = $cmd || ($dot 
 &amp;&amp; $Last_Shell) || &amp;prompt(&#39;|&#39;);

# perltidy -bol [default]
    return
      unless $cmd = $cmd
      || ( $dot
        &amp;&amp; $Last_Shell )
      || &amp;prompt(&#39;|&#39;);

# perltidy -nbol
 return unless $cmd = $cmd || ( $dot &amp;&amp; $Last_Shell ) || &amp;prompt(&#39;|&#39;);</code></pre>

</dd>
<dt id="bom---break-at-old-method-breakpoints">-bom, --break-at-old-method-breakpoints</dt>
<dd>

By default, a method call arrow <code>-&gt;</code> is considered a candidate for a breakpoint, but method chains will fill to the line width before a break is considered. With -bom, breaks before the arrow are preserved, so if you have preformatted a method chain:

<pre><code> my $q = $rs
 -&gt;related_resultset(&#39;CDs&#39;)
 -&gt;related_resultset(&#39;Tracks&#39;)
 -&gt;search({
 &#39;track.id&#39; =&gt; {-ident =&gt; &#39;none_search.id&#39;},
 })-&gt;as_query;</code></pre>

It will keep these breaks, rather than become this:

<pre><code> my $q = $rs-&gt;related_resultset(&#39;CDs&#39;)-&gt;related_resultset(&#39;Tracks&#39;)-&gt;search({
 &#39;track.id&#39; =&gt; {-ident =&gt; &#39;none_search.id&#39;},
 })-&gt;as_query;</code></pre>

This flag will also look for and keep a &#39;cuddled&#39; style of calls, in which lines begin with a closing paren followed by a call arrow, as in this example:

<pre><code> my $q = $rs-&gt;related_resultset(
 &#39;CDs&#39;
 )-&gt;related_resultset(
 &#39;Tracks&#39;
 )-&gt;search( {
 &#39;track.id&#39; =&gt; { -ident =&gt; &#39;none_search.id&#39; },
 } )-&gt;as_query;</code></pre>

You may want to include the -weld-nested-containers flag in this case to keep nested braces and parens together, as in the last line.

</dd>
<dt id="bos---break-at-old-semicolon-breakpoints">-bos, --break-at-old-semicolon-breakpoints</dt>
<dd>

Semicolons are normally placed at the end of a statement. This means that formatted lines do not normally begin with semicolons. If the input stream has some lines which begin with semicolons, these can be retained by setting this flag. For example, consider the following two-line input snippet:

The default formatting will be:

The result using perltidy -bos keeps the isolated semicolon:

The default is not to do this, -nbos.

</dd>
<dt id="bok---break-at-old-keyword-breakpoints">-bok, --break-at-old-keyword-breakpoints</dt>
<dd>

By default, perltidy will retain a breakpoint before keywords which may return lists, such as <code>sort</code> and &lt;map&gt;. This allows chains of these operators to be displayed one per line. Use -nbok to prevent retaining these breakpoints.

</dd>
<dt id="bot---break-at-old-ternary-breakpoints">-bot, --break-at-old-ternary-breakpoints</dt>
<dd>

By default, if a conditional (ternary) operator is broken at a <code>:</code>, then it will remain broken. To prevent this, and thereby form longer lines, use -nbot.

</dd>
<dt id="boa---break-at-old-attribute-breakpoints">-boa, --break-at-old-attribute-breakpoints</dt>
<dd>

By default, if an attribute list is broken at a <code>:</code> in the source file, then it will remain broken. For example, given the following code, the line breaks at the &#39;:&#39;s will be retained:

<pre><code> my @field
 : field
 : Default(1)
 : Get(&#39;Name&#39; =&gt; &#39;foo&#39;) : Set(&#39;Name&#39;);</code></pre>

If the attributes are on a single line in the source code then they will remain on a single line if possible.

To prevent this, and thereby always form longer lines, use -nboa.

</dd>
<dt id="Keeping-old-breakpoints-at-specific-token-types">Keeping old breakpoints at specific token types</dt>
<dd>

Two command line parameters provide detailed control over whether perltidy should keep an old line break before or after a specific token type:

-kbb=s or --keep-old-breakpoints-before=s, and

-kba=s or --keep-old-breakpoints-after=s

For example, -kbb=&#39;=&gt;&#39; means that if an input line begins with a &#39;=&gt;&#39; then the output script should also have a line break before that token.

For example, given the script:

<pre><code> method &#39;foo&#39;
 =&gt; [ Int, Int ]
 =&gt; sub {
 my ( $self, $x, $y ) = ( shift, @_ );
 ...;
 };

# perltidy [default]
    method &#39;foo&#39; =&gt; [ Int, Int ] =&gt; sub {
        my ( $self, $x, $y ) = ( shift, @_ );
        ...;
    };

# perltidy -kbb=&#39;=&gt;&#39;
 method &#39;foo&#39;
 =&gt; [ Int, Int ]
 =&gt; sub {
 my ( $self, $x, $y ) = ( shift, @_ );
 ...;
 };</code></pre>

</dd>
<dt id="iob---ignore-old-breakpoints">-iob, --ignore-old-breakpoints</dt>
<dd>

Use this flag to tell perltidy to ignore existing line breaks to the maximum extent possible. This will tend to produce the longest possible containers, regardless of type, which do not exceed the line length limit. But please note that this parameter has priority over all other parameters requesting that certain old breakpoints be kept.

</dd>
<dt id="kis---keep-interior-semicolons">-kis, --keep-interior-semicolons</dt>
<dd>

Use the -kis flag to prevent breaking at a semicolon if there was no break there in the input file. Normally perltidy places a newline after each semicolon which terminates a statement unless several statements are contained within a one-line brace block. To illustrate, consider the following input lines:

<pre><code> dbmclose(%verb_delim); undef %verb_delim;
 dbmclose(%expanded); undef %expanded;</code></pre>

The default is to break after each statement, giving

<pre><code> dbmclose(%verb_delim);
 undef %verb_delim;
 dbmclose(%expanded);
 undef %expanded;</code></pre>

With perltidy -kis the multiple statements are retained:

<pre><code> dbmclose(%verb_delim); undef %verb_delim;
 dbmclose(%expanded); undef %expanded;</code></pre>

The statements are still subject to the specified value of maximum-line-length and will be broken if this maximum is exceeded.

</dd>
</dl>

<h2 id="Blank-Line-Control">Blank Line Control</h2>

Blank lines can improve the readability of a script if they are carefully placed. Perltidy has several commands for controlling the insertion, retention, and removal of blank lines.

<dl>

<dt id="fbl---freeze-blank-lines">-fbl, --freeze-blank-lines</dt>
<dd>

Set -fbl if you want to the blank lines in your script to remain exactly as they are. The rest of the parameters in this section may then be ignored. (Note: setting the -fbl flag is equivalent to setting -mbl=0 and -kbl=2).

</dd>
<dt id="bbc---blanks-before-comments">-bbc, --blanks-before-comments</dt>
<dd>

A blank line will be introduced before a full-line comment. This is the default. Use -nbbc or --noblanks-before-comments to prevent such blank lines from being introduced.

</dd>
<dt id="blbs-n---blank-lines-before-subs-n">-blbs=n, --blank-lines-before-subs=n</dt>
<dd>

The parameter -blbs=n requests that least n blank lines precede a sub definition which does not follow a comment and which is more than one-line long. The default is &lt;-blbs=1&gt;. BEGIN and END blocks are included.

The requested number of blanks statement will be inserted regardless of the value of --maximum-consecutive-blank-lines=n (-mbl=n) with the exception that if -mbl=0 then no blanks will be output.

This parameter interacts with the value k of the parameter --maximum-consecutive-blank-lines=k (-mbl=k) as follows:

1. If -mbl=0 then no blanks will be output. This allows all blanks to be suppressed with a single parameter. Otherwise,

2. If the number of old blank lines in the script is less than n then additional blanks will be inserted to make the total n regardless of the value of -mbl=k.

3. If the number of old blank lines in the script equals or exceeds n then this parameter has no effect, however the total will not exceed value specified on the -mbl=k flag.

</dd>
<dt id="blbp-n---blank-lines-before-packages-n">-blbp=n, --blank-lines-before-packages=n</dt>
<dd>

The parameter -blbp=n requests that least n blank lines precede a package which does not follow a comment. The default is -blbp=1.

This parameter interacts with the value k of the parameter --maximum-consecutive-blank-lines=k (-mbl=k) in the same way as described for the previous item -blbs=n.

</dd>
<dt id="bbs---blanks-before-subs">-bbs, --blanks-before-subs</dt>
<dd>

For compatibility with previous versions, -bbs or --blanks-before-subs is equivalent to -blbp=1 and -blbs=1.

Likewise, -nbbs or --noblanks-before-subs is equivalent to -blbp=0 and -blbs=0.

</dd>
<dt id="bbb---blanks-before-blocks">-bbb, --blanks-before-blocks</dt>
<dd>

A blank line will be introduced before blocks of coding delimited by for, foreach, while, until, and if, unless, in the following circumstances:

<ul>

<li>The block is not preceded by a comment.

</li>
<li>The block is not a one-line block.

</li>
<li>The number of consecutive non-blank lines at the current indentation depth is at least -lbl (see next section).

</li>
</ul>

This is the default. The intention of this option is to introduce some space within dense coding. This is negated with -nbbb or --noblanks-before-blocks.

</dd>
<dt id="lbl-n---long-block-line-count-n">-lbl=n --long-block-line-count=n</dt>
<dd>

This controls how often perltidy is allowed to add blank lines before certain block types (see previous section). The default is 8. Entering a value of 0 is equivalent to entering a very large number.

</dd>
<dt id="blao-i-or---blank-lines-after-opening-block-i">-blao=i or --blank-lines-after-opening-block=i</dt>
<dd>

This control places a minimum of i blank lines after a line which ends with an opening block brace of a specified type. By default, this only applies to the block of a named sub, but this can be changed (see -blaol below). The default is not to do this (i=0).

Please see the note below on using the -blao and -blbc options.

</dd>
<dt id="blbc-i-or---blank-lines-before-closing-block-i">-blbc=i or --blank-lines-before-closing-block=i</dt>
<dd>

This control places a minimum of i blank lines before a line which begins with a closing block brace of a specified type. By default, this only applies to the block of a named sub, but this can be changed (see -blbcl below). The default is not to do this (i=0).

</dd>
<dt id="blaol-s-or---blank-lines-after-opening-block-list-s">-blaol=s or --blank-lines-after-opening-block-list=s</dt>
<dd>

The parameter s is a list of block type keywords to which the flag -blao should apply. The section <a href="#Specifying-Block-Types">&quot;Specifying Block Types&quot;</a> explains how to list block types.

</dd>
<dt id="blbcl-s-or---blank-lines-before-closing-block-list-s">-blbcl=s or --blank-lines-before-closing-block-list=s</dt>
<dd>

This parameter is a list of block type keywords to which the flag -blbc should apply. The section <a href="#Specifying-Block-Types">&quot;Specifying Block Types&quot;</a> explains how to list block types.

</dd>
<dt id="Note-on-using-the--blao-and--blbc-options">Note on using the -blao and -blbc options.</dt>
<dd>

These blank line controls introduce a certain minimum number of blank lines in the text, but the final number of blank lines may be greater, depending on values of the other blank line controls and the number of old blank lines. A consequence is that introducing blank lines with these and other controls cannot be exactly undone, so some experimentation with these controls is recommended before using them.

For example, suppose that for some reason we decide to introduce one blank space at the beginning and ending of all blocks. We could do this using

<pre><code> perltidy -blao=2 -blbc=2 -blaol=&#39;*&#39; -blbcl=&#39;*&#39; filename</code></pre>

Now suppose the script continues to be developed, but at some later date we decide we don&#39;t want these spaces after all. we might expect that running with the flags -blao=0 and -blbc=0 will undo them. However, by default perltidy retains single blank lines, so the blank lines remain.

We can easily fix this by telling perltidy to ignore old blank lines by including the added parameter -kbl=0 and rerunning. Then the unwanted blank lines will be gone. However, this will cause all old blank lines to be ignored, perhaps even some that were added by hand to improve formatting. So please be cautious when using these parameters.

</dd>
<dt id="mbl-n---maximum-consecutive-blank-lines-n">-mbl=n --maximum-consecutive-blank-lines=n</dt>
<dd>

This parameter specifies the maximum number of consecutive blank lines which will be output within code sections of a script. The default is n=1. If the input file has more than n consecutive blank lines, the number will be reduced to n except as noted above for the -blbp and -blbs parameters. If n=0 then no blank lines will be output (unless all old blank lines are retained with the -kbl=2 flag of the next section).

This flag obviously does not apply to pod sections, here-documents, and quotes.

</dd>
<dt id="kbl-n---keep-old-blank-lines-n">-kbl=n, --keep-old-blank-lines=n</dt>
<dd>

The -kbl=n flag gives you control over how your existing blank lines are treated.

The possible values of n are:

<pre><code> n=0 ignore all old blank lines
 n=1 stable: keep old blanks, but limited by the value of the B&lt;-mbl=n&gt; flag
 n=2 keep all old blank lines, regardless of the value of the B&lt;-mbl=n&gt; flag</code></pre>

The default is n=1.

</dd>
<dt id="sob---swallow-optional-blank-lines">-sob, --swallow-optional-blank-lines</dt>
<dd>

This is equivalent to kbl=0 and is included for compatibility with previous versions.

</dd>
<dt id="nsob---noswallow-optional-blank-lines">-nsob, --noswallow-optional-blank-lines</dt>
<dd>

This is equivalent to kbl=1 and is included for compatibility with previous versions.

</dd>
</dl>

Controls for blank lines around lines of consecutive keywords

The parameters in this section provide some control over the placement of blank lines within and around groups of statements beginning with selected keywords. These blank lines are called here keyword group blanks, and all of the parameters begin with --keyword-group-blanks*, or -kgb* for short. The default settings do not employ these controls but they can be enabled with the following parameters:

-kgbl=s or --keyword-group-blanks-list=s; s is a quoted string of keywords

-kgbs=s or --keyword-group-blanks-size=s; s gives the number of keywords required to form a group.

-kgbb=n or --keyword-group-blanks-before=n; n = (0, 1, or 2) controls a leading blank

-kgba=n or --keyword-group-blanks-after=n; n = (0, 1, or 2) controls a trailing blank

-kgbi or --keyword-group-blanks-inside is a switch for adding blanks between subgroups

-kgbd or --keyword-group-blanks-delete is a switch for removing initial blank lines between keywords

-kgbr=n or --keyword-group-blanks-repeat-count=n can limit the number of times this logic is applied

In addition, the following abbreviations are available to for simplified usage:

-kgb or --keyword-group-blanks is short for -kgbb=2 -kgba=2 kgbi

-nkgb or --nokeyword-group-blanks, is short for -kgbb=1 -kgba=1 nkgbi

Before describing the meaning of the parameters in detail let us look at an example which is formatted with default parameter settings.

<pre><code> print &quot;Entering test 2\n&quot;;
 use Test;
 use Encode qw(from_to encode decode
 encode_utf8 decode_utf8
 find_encoding is_utf8);
 use charnames qw(greek);
 my @encodings = grep( /iso-?8859/, Encode::encodings() );
 my @character_set = ( &#39;0&#39; .. &#39;9&#39;, &#39;A&#39; .. &#39;Z&#39;, &#39;a&#39; .. &#39;z&#39; );
 my @source = qw(ascii iso8859-1 cp1250);
 my @destiny = qw(cp1047 cp37 posix-bc);
 my @ebcdic_sets = qw(cp1047 cp37 posix-bc);
 my $str = join( &#39;&#39;, map( chr($_), 0x20 .. 0x7E ) );
 return unless ($str);</code></pre>

using perltidy -kgb gives:

<pre><code> print &quot;Entering test 2\n&quot;;
 &lt;----------this blank controlled by -kgbb
 use Test;
 use Encode qw(from_to encode decode
 encode_utf8 decode_utf8
 find_encoding is_utf8);
 use charnames qw(greek);
 &lt;---------this blank controlled by -kgbi
 my @encodings = grep( /iso-?8859/, Encode::encodings() );
 my @character_set = ( &#39;0&#39; .. &#39;9&#39;, &#39;A&#39; .. &#39;Z&#39;, &#39;a&#39; .. &#39;z&#39; );
 my @source = qw(ascii iso8859-1 cp1250);
 my @destiny = qw(cp1047 cp37 posix-bc);
 my @ebcdic_sets = qw(cp1047 cp37 posix-bc);
 my $str = join( &#39;&#39;, map( chr($_), 0x20 .. 0x7E ) );
 &lt;----------this blank controlled by -kgba
 return unless ($str);</code></pre>

Blank lines have been introduced around the my and use sequences. What happened is that the default keyword list includes my and use but not print and return. So a continuous sequence of nine my and use statements was located. This number exceeds the default threshold of five, so blanks were placed before and after the entire group. Then, since there was also a subsequence of six my lines, a blank line was introduced to separate them.

Finer control over blank placement can be achieved by using the individual parameters rather than the -kgb flag. The individual controls are as follows.

-kgbl=s or --keyword-group-blanks-list=s, where s is a quoted string, defines the set of keywords which will be formed into groups. The string is a space separated list of keywords. The default set is s=&quot;use require local our my&quot;, but any list of keywords may be used. Comment lines may also be included in a keyword group, even though they are not keywords. To include ordinary block comments, include the symbol BC. To include static block comments (which normally begin with &#39;##&#39;), include the symbol SBC.

-kgbs=s or --keyword-group-blanks-size=s, where s is a string describing the number of consecutive keyword statements forming a group. If s is an integer then it is the minimum number required for a group. A maximum value may also be given with the format s=min.max, where min is the minimum number and max is the maximum number, and the min and max values are separated by one or more dots. No groups will be found if the maximum is less than the minimum. The maximum is unlimited if not given. The default is s=5. Some examples:

<pre><code> s min max number for group
 3 3 unlimited 3 or more
 1.1 1 1 1
 1..3 1 3 1 to 3
 1.0 1 0 (no match)
 </code></pre>

-kgbb=n or --keyword-group-blanks-before=n specifies whether a blank should appear before the first line of the group, as follows:

<pre><code> n=0 =&gt; (delete) an existing blank line will be removed
 n=1 =&gt; (stable) no change to the input file is made [DEFAULT]
 n=2 =&gt; (insert) a blank line is introduced if possible</code></pre>

-kgba=n or --keyword-group-blanks-after=n likewise specifies whether a blank should appear after the last line of the group, using the same scheme (0=delete, 1=stable, 2=insert).

-kgbi or --keyword-group-blanks-inside controls the insertion of blank lines between the first and last statement of the entire group. If there is a continuous run of a single statement type with more than the minimum threshold number (as specified with -kgbs=s) then this switch causes a blank line be inserted between this subgroup and the others. In the example above this happened between the use and my statements.

-kgbd or --keyword-group-blanks-delete controls the deletion of any blank lines that exist in the the group when it is first scanned. When statements are initially scanned, any existing blank lines are included in the collection. Any such orignial blank lines will be deleted before any other insertions are made when the parameter -kgbd is set. The default is not to do this, -nkgbd.

-kgbr=n or --keyword-group-blanks-repeat-count=n specifies n, the maximum number of times this logic will be applied to any file. The special value n=0 is the same as n=infinity which means it will be applied to an entire script [Default]. A value n=1 could be used to make it apply just one time for example. This might be useful for adjusting just the use statements in the top part of a module for example.

-kgb or --keyword-group-blanks is an abbreviation equivalent to setting -kgbb=1 -kgba=1 -kgbi. This turns on keyword group formatting with a set of default values.

-nkgb or --nokeyword-group-blanks is equivalent to -kgbb=0 -kgba nkgbi. This flag turns off keyword group blank lines and is the default setting.

Here are a few notes about the functioning of this technique.

<ul>

<li>These parameters are probably more useful as part of a major code reformatting operation rather than as a routine formatting operation.

In particular, note that deleting old blank lines with -kgbd is an irreversible operation so it should be applied with care. Existing blank lines may be serving an important role in controlling vertical alignment.

</li>
<li>Conflicts which arise among these kgb* parameters and other blank line controls are generally resolved by producing the maximum number of blank lines implied by any parameter.

For example, if the flags --freeze-blank-lines, or --keep-old-blank-lines=2, are set, then they have priority over any blank line deletion implied by the -kgb flags of this section, so no blank lines will be deleted.

For another example, if a keyword group ends at a sub and the flag kgba=0 requests no blank line there, but we also have --blank-lines-before-subs=2, then two blank lines will still be introduced before the sub.

</li>
<li>The introduction of blank lines does not occur if it would conflict with other input controls or code validity. For example, a blank line will not be placed within a here-doc or within a section of code marked with format skipping comments. And in general, a blank line will only be introduced at the end of a group if the next statement is a line of code.

</li>
<li>The count which is used to determine the group size is not the number of lines but rather the total number of keywords which are found. Individual statements with a certain leading keyword may continue on multiple lines, but if any of these lines is nested more than one level deep then that group will be ended.

</li>
<li>The search for groups of lines with similar leading keywords is based on the input source, not the final formatted source. Consequently, if the source code is badly formatted, it would be best to make a first formatting pass without these options.

</li>
</ul>

<h2 id="Styles">Styles</h2>

A style refers to a convenient collection of existing parameters.

<dl>

<dt id="gnu---gnu-style">-gnu, --gnu-style</dt>
<dd>

-gnu gives an approximation to the GNU Coding Standards (which do not apply to perl) as they are sometimes implemented. At present, this style overrides the default style with the following parameters:

</dd>
<dt id="pbp---perl-best-practices">-pbp, --perl-best-practices</dt>
<dd>

-pbp is an abbreviation for the parameters in the book Perl Best Practices by Damian Conway:

Please note that this parameter set includes -st and -se flags, which make perltidy act as a filter on one file only. These can be overridden by placing -nst and/or -nse after the -pbp parameter.

Also note that the value of continuation indentation, -ci=4, is equal to the value of the full indentation, -i=4. It is recommended that the either (1) the parameter -ci=2 be used instead, or the flag -xci be set. This will help show structure, particularly when there are ternary statements. The following snippet illustrates these options.

<pre><code> # perltidy -pbp
 $self-&gt;{_text} = (
 !$section ? &#39;&#39;
 : $type eq &#39;item&#39; ? &quot;the $section entry&quot;
 : &quot;the section on $section&quot;
 )
 . (
 $page
 ? ( $section ? &#39; in &#39; : &#39;&#39; ) . &quot;the $page$page_ext manpage&quot;
 : &#39; elsewhere in this document&#39;
 );

# perltidy -pbp -ci=2
    $self-&gt;{_text} = (
         !$section        ? &#39;&#39;
        : $type eq &#39;item&#39; ? &quot;the $section entry&quot;
        :                   &quot;the section on $section&quot;
      )
      . (
        $page
        ? ( $section ? &#39; in &#39; : &#39;&#39; ) . &quot;the $page$page_ext manpage&quot;
        : &#39; elsewhere in this document&#39;
      );

# perltidy -pbp -xci
 $self-&gt;{_text} = (
 !$section ? &#39;&#39;
 : $type eq &#39;item&#39; ? &quot;the $section entry&quot;
 : &quot;the section on $section&quot;
 )
 . ( $page
 ? ( $section ? &#39; in &#39; : &#39;&#39; ) . &quot;the $page$page_ext manpage&quot;
 : &#39; elsewhere in this document&#39;
 );</code></pre>

The -xci flag was developed after the -pbp parameters were published so you need to include it separately.

</dd>
<dt id="One-line-blocks">One-line blocks</dt>
<dd>

There are a few points to note regarding one-line blocks. A one-line block is something like this,

where the contents within the curly braces is short enough to fit on a single line.

With few exceptions, perltidy retains existing one-line blocks, if it is possible within the line-length constraint, but it does not attempt to form new ones. In other words, perltidy will try to follow the one-line block style of the input file.

If an existing one-line block is longer than the maximum line length, however, it will be broken into multiple lines. When this happens, perltidy checks for and adds any optional terminating semicolon (unless the -nasc option is used) if the block is a code block.

The main exception is that perltidy will attempt to form new one-line blocks following the keywords <code>map</code>, <code>eval</code>, and <code>sort</code>, because these code blocks are often small and most clearly displayed in a single line.

One-line block rules can conflict with the cuddled-else option. When the cuddled-else option is used, perltidy retains existing one-line blocks, even if they do not obey cuddled-else formatting.

Occasionally, when one-line blocks get broken because they exceed the available line length, the formatting will violate the requested brace style. If this happens, reformatting the script a second time should correct the problem.

Sometimes it might be desirable to convert a script to have one-line blocks whenever possible. Although there is currently no flag for this, a simple workaround is to execute perltidy twice, once with the flag -noadd-newlines and then once again with normal parameters, like this:

<pre><code> cat infile | perltidy -nanl | perltidy &gt;outfile</code></pre>

When executed on this snippet

<pre><code> if ( $? == -1 ) {
 die &quot;failed to execute: $!\n&quot;;
 }
 if ( $? == -1 ) {
 print &quot;Had enough.\n&quot;;
 die &quot;failed to execute: $!\n&quot;;
 }</code></pre>

the result is

<pre><code> if ( $? == -1 ) { die &quot;failed to execute: $!\n&quot;; }
 if ( $? == -1 ) {
 print &quot;Had enough.\n&quot;;
 die &quot;failed to execute: $!\n&quot;;
 }</code></pre>

This shows that blocks with a single statement become one-line blocks.

</dd>
<dt id="olbs-n---one-line-block-semicolons-n">-olbs=n, --one-line-block-semicolons=n</dt>
<dd>

This flag controls the placement of semicolons at the end of one-line blocks. Semicolons are optional before a closing block brace, and frequently they are omitted at the end of a one-line block containing just a single statement. By default, perltidy follows the input file regarding these semicolons, but this behavior can be controlled by this flag. The values of n are:

<pre><code> n=0 remove terminal semicolons in one-line blocks having a single statement
 n=1 stable; keep input file placement of terminal semicolons [DEFAULT ]
 n=2 add terminal semicolons in all one-line blocks</code></pre>

Note that the n=2 option has no effect if adding semicolons is prohibited with the -nasc flag. Also not that while n=2 adds missing semicolons to all one-line blocks, regardless of complexity, the n=0 option only removes ending semicolons which terminate one-line blocks containing just one semicolon. So these two options are not exact inverses.

</dd>
<dt id="olbn-n---one-line-block-nesting-n">-olbn=n, --one-line-block-nesting=n</dt>
<dd>

Nested one-line blocks are lines with code blocks which themselves contain code blocks. For example, the following line is a nested one-line block.

<pre><code> foreach (@list) { if ($_ eq $asked_for) { last } ++$found }</code></pre>

The default behavior is to break such lines into multiple lines, but this behavior can be controlled with this flag. The values of n are:

<pre><code> n=0 break nested one-line blocks into multiple lines [DEFAULT]
 n=1 stable: keep existing nested-one line blocks intact</code></pre>

For the above example, the default formatting (-olbn=0) is

<pre><code> foreach (@list) {
 if ( $_ eq $asked_for ) { last }
 ++$found;
 }</code></pre>

If the parameter -olbn=1 is given, then the line will be left intact if it is a single line in the source, or it will be broken into multiple lines if it is broken in multiple lines in the source.

</dd>
</dl>

<h2 id="Controlling-Vertical-Alignment">Controlling Vertical Alignment</h2>

Vertical alignment refers to lining up certain symbols in a list of consecutive similar lines to improve readability. For example, the &quot;fat commas&quot; are aligned in the following statement:

<pre><code> $data = $pkg-&gt;new(
 PeerAddr =&gt; join( &quot;.&quot;, @port[ 0 .. 3 ] ), 
 PeerPort =&gt; $port[4] * 256 + $port[5],
 Proto =&gt; &#39;tcp&#39;
 );</code></pre>

The only explicit control on vertical alignment is to turn it off using -novalign, a flag mainly intended for debugging. However, vertical alignment can be forced to stop and restart by selectively introducing blank lines. For example, a blank has been inserted in the following code to keep somewhat similar things aligned.

<pre><code> %option_range = (
 &#39;format&#39; =&gt; [ &#39;tidy&#39;, &#39;html&#39;, &#39;user&#39; ],
 &#39;output-line-ending&#39; =&gt; [ &#39;dos&#39;, &#39;win&#39;, &#39;mac&#39;, &#39;unix&#39; ],
 &#39;character-encoding&#39; =&gt; [ &#39;none&#39;, &#39;utf8&#39; ],

&#39;block-brace-tightness&#39; =&gt; [ 0, 2 ],
 &#39;brace-tightness&#39; =&gt; [ 0, 2 ],
 &#39;paren-tightness&#39; =&gt; [ 0, 2 ],
 &#39;square-bracket-tightness&#39; =&gt; [ 0, 2 ],
 );</code></pre>

<h2 id="Other-Controls">Other Controls</h2>

<dl>

<dt id="Deleting-selected-text">Deleting selected text</dt>
<dd>

Perltidy can selectively delete comments and/or pod documentation. The command -dac or --delete-all-comments will delete all comments and all pod documentation, leaving just code and any leading system control lines.

The command -dp or --delete-pod will remove all pod documentation (but not comments).

Two commands which remove comments (but not pod) are: -dbc or --delete-block-comments and -dsc or --delete-side-comments. (Hanging side comments will be deleted with side comments here.)

The negatives of these commands also work, and are the defaults. When block comments are deleted, any leading &#39;hash-bang&#39; will be retained. Also, if the -x flag is used, any system commands before a leading hash-bang will be retained (even if they are in the form of comments).

</dd>
<dt id="Writing-selected-text-to-a-file">Writing selected text to a file</dt>
<dd>

When perltidy writes a formatted text file, it has the ability to also send selected text to a file with a .TEE extension. This text can include comments and pod documentation.

The command -tac or --tee-all-comments will write all comments and all pod documentation.

The command -tp or --tee-pod will write all pod documentation (but not comments).

The commands which write comments (but not pod) are: -tbc or --tee-block-comments and -tsc or --tee-side-comments. (Hanging side comments will be written with side comments here.)

The negatives of these commands also work, and are the defaults.

</dd>
<dt id="Using-a-.perltidyrc-command-file">Using a .perltidyrc command file</dt>
<dd>

If you use perltidy frequently, you probably won&#39;t be happy until you create a .perltidyrc file to avoid typing commonly-used parameters. Perltidy will first look in your current directory for a command file named .perltidyrc. If it does not find one, it will continue looking for one in other standard locations.

These other locations are system-dependent, and may be displayed with the command <code>perltidy -dpro</code>. Under Unix systems, it will first look for an environment variable PERLTIDY. Then it will look for a .perltidyrc file in the home directory, and then for a system-wide file /usr/local/etc/perltidyrc, and then it will look for /etc/perltidyrc. Note that these last two system-wide files do not have a leading dot. Further system-dependent information will be found in the INSTALL file distributed with perltidy.

Under Windows, perltidy will also search for a configuration file named perltidy.ini since Windows does not allow files with a leading period (.). Use <code>perltidy -dpro</code> to see the possible locations for your system. An example might be C:\Documents and Settings\All Users\perltidy.ini.

Another option is the use of the PERLTIDY environment variable. The method for setting environment variables depends upon the version of Windows that you are using. Instructions for Windows 95 and later versions can be found here:

http://www.netmanage.com/000/20021101_005_tcm21-6336.pdf

Under Windows NT / 2000 / XP the PERLTIDY environment variable can be placed in either the user section or the system section. The later makes the configuration file common to all users on the machine. Be sure to enter the full path of the configuration file in the value of the environment variable. Ex. PERLTIDY=C:\Documents and Settings\perltidy.ini

The configuration file is free format, and simply a list of parameters, just as they would be entered on a command line. Any number of lines may be used, with any number of parameters per line, although it may be easiest to read with one parameter per line. Comment text begins with a #, and there must also be a space before the # for side comments. It is a good idea to put complex parameters in either single or double quotes.

Here is an example of a .perltidyrc file:

<pre><code> # This is a simple of a .perltidyrc configuration file
 # This implements a highly spaced style
 -se # errors to standard error output
 -w # show all warnings
 -bl # braces on new lines
 -pt=0 # parens not tight at all
 -bt=0 # braces not tight
 -sbt=0 # square brackets not tight</code></pre>

The parameters in the .perltidyrc file are installed first, so any parameters given on the command line will have priority over them.

To avoid confusion, perltidy ignores any command in the .perltidyrc file which would cause some kind of dump and an exit. These are:

There are several options may be helpful in debugging a .perltidyrc file:

<ul>

<li>A very helpful command is --dump-profile or -dpro. It writes a list of all configuration filenames tested to standard output, and if a file is found, it dumps the content to standard output before exiting. So, to find out where perltidy looks for its configuration files, and which one if any it selects, just enter

<pre><code> perltidy -dpro</code></pre>

</li>
<li>It may be simplest to develop and test configuration files with alternative names, and invoke them with -pro=filename on the command line. Then rename the desired file to .perltidyrc when finished.

</li>
<li>The parameters in the .perltidyrc file can be switched off with the -npro option.

</li>
<li>The commands --dump-options, --dump-defaults, --dump-long-names, and --dump-short-names, all described below, may all be helpful.

</li>
</ul>

</dd>
<dt id="Creating-a-new-abbreviation">Creating a new abbreviation</dt>
<dd>

A special notation is available for use in a .perltidyrc file for creating an abbreviation for a group of options. This can be used to create a shorthand for one or more styles which are frequently, but not always, used. The notation is to group the options within curly braces which are preceded by the name of the alias (without leading dashes), like this:

<pre><code> newword {
 -opt1
 -opt2
 }</code></pre>

where newword is the abbreviation, and opt1, etc, are existing parameters or other abbreviations. The main syntax requirement is that the new abbreviation along with its opening curly brace must begin on a new line. Space before and after the curly braces is optional. For a specific example, the following line

could be placed in a .perltidyrc file, and then invoked at will with

<pre><code> perltidy -airy somefile.pl</code></pre>

(Either <code>-airy</code> or <code>--airy</code> may be used).

</dd>
<dt id="Skipping-leading-non-perl-commands-with--x-or---look-for-hash-bang">Skipping leading non-perl commands with -x or --look-for-hash-bang</dt>
<dd>

If your script has leading lines of system commands or other text which are not valid perl code, and which are separated from the start of the perl code by a &quot;hash-bang&quot; line, ( a line of the form <code>#!...perl</code> ), you must use the -x flag to tell perltidy not to parse and format any lines before the &quot;hash-bang&quot; line. This option also invokes perl with a -x flag when checking the syntax. This option was originally added to allow perltidy to parse interactive VMS scripts, but it should be used for any script which is normally invoked with <code>perl -x</code>.

Please note: do not use this flag unless you are sure your script needs it. Parsing errors can occur if it does not have a hash-bang, or, for example, if the actual first hash-bang is in a here-doc. In that case a parsing error will occur because the tokenization will begin in the middle of the here-doc.

</dd>
<dt id="Making-a-file-unreadable">Making a file unreadable</dt>
<dd>

The goal of perltidy is to improve the readability of files, but there are two commands which have the opposite effect, --mangle and --extrude. They are actually merely aliases for combinations of other parameters. Both of these strip all possible whitespace, but leave comments and pod documents, so that they are essentially reversible. The difference between these is that --mangle puts the fewest possible line breaks in a script while --extrude puts the maximum possible. Note that these options do not provided any meaningful obfuscation, because perltidy can be used to reformat the files. They were originally developed to help test the tokenization logic of perltidy, but they have other uses. One use for --mangle is the following:

<pre><code> perltidy --mangle myfile.pl -st | perltidy -o myfile.pl.new</code></pre>

This will form the maximum possible number of one-line blocks (see next section), and can sometimes help clean up a badly formatted script.

A similar technique can be used with --extrude instead of --mangle to make the minimum number of one-line blocks.

Another use for --mangle is to combine it with -dac to reduce the file size of a perl script.

</dd>
<dt id="Debugging">Debugging</dt>
<dd>

The following flags are available for debugging:

--dump-cuddled-block-list or -dcbl will dump to standard output the internal hash of cuddled block types created by a -cuddled-block-list input string.

--dump-defaults or -ddf will write the default option set to standard output and quit

--dump-profile or -dpro will write the name of the current configuration file and its contents to standard output and quit.

--dump-options or -dop will write current option set to standard output and quit.

--dump-long-names or -dln will write all command line long names (passed to Get_options) to standard output and quit.

--dump-short-names or -dsn will write all command line short names to standard output and quit.

--dump-token-types or -dtt will write a list of all token types to standard output and quit.

--dump-want-left-space or -dwls will write the hash %want_left_space to standard output and quit. See the section on controlling whitespace around tokens.

--dump-want-right-space or -dwrs will write the hash %want_right_space to standard output and quit. See the section on controlling whitespace around tokens.

--no-memoize or -nmem will turn of memoizing. Memoization can reduce run time when running perltidy repeatedly in a single process. It is on by default but can be deactivated for testing with -nmem.

--no-timestamp or -nts will eliminate any time stamps in output files to prevent differences in dates from causing test installation scripts to fail. There are just a couple of places where timestamps normally occur. One is in the headers of html files, and another is when the -cscw option is selected. The default is to allow timestamps (--timestamp or -ts).

--file-size-order or -fso will cause files to be processed in order of increasing size, when multiple files are being processed. This is useful during program development, when large numbers of files with varying sizes are processed, because it can reduce virtual memory usage.

--maximum-file-size-mb=n or -maxfs=n specifies the maximum file size in megabytes that perltidy will attempt to format. This parameter is provided to avoid causing system problems by accidentally attempting to format an extremely large data file. Most perl scripts are less than about 2 MB in size. The integer n has a default value of 10, so perltidy will skip formatting files which have a size greater than 10 MB. The command to increase the limit to 20 MB for example would be

<pre><code> perltidy -maxfs=20</code></pre>

This only applies to files specified by filename on the command line.

--maximum-level-errors=n or -maxle=n specifies the maximum number of indentation level errors are allowed before perltidy skips formatting and just outputs a file verbatim. The default is n=1. This means that if the final indentation of a script differs from the starting indentation by more than 1 levels, the file will be output verbatim. To avoid formatting if there are any indentation level errors use -maxle=0. To skip this check you can either set n equal to a large number, such as n=100, or set n=-1.

For example, the following script has level error of 3 and will be output verbatim

<pre><code> Input and default output:
 {{{

perltidy -maxle=100
 {
 {
 {</code></pre>

--maximum-unexpected-errors=n or -maxue=n specifies the maximum number of unexpected tokenization errors are allowed before formatting is skipped and a script is output verbatim. The intention is to avoid accidentally formatting a non-perl script, such as an html file for example. This check can be turned off by setting n=0.

A recommended value is n=3. However, the default is n=0 (skip this check) to avoid causing problems with scripts which have extended syntaxes.

-DEBUG will write a file with extension .DEBUG for each input file showing the tokenization of all lines of code.

</dd>
<dt id="Working-with-MakeMaker-AutoLoader-and-SelfLoader">Working with MakeMaker, AutoLoader and SelfLoader</dt>
<dd>

The first $VERSION line of a file which might be eval&#39;d by MakeMaker is passed through unchanged except for indentation. Use --nopass-version-line, or -npvl, to deactivate this feature.

If the AutoLoader module is used, perltidy will continue formatting code after seeing an __END__ line. Use --nolook-for-autoloader, or -nlal, to deactivate this feature.

Likewise, if the SelfLoader module is used, perltidy will continue formatting code after seeing a __DATA__ line. Use --nolook-for-selfloader, or -nlsl, to deactivate this feature.

</dd>
<dt id="Working-around-problems-with-older-version-of-Perl">Working around problems with older version of Perl</dt>
<dd>

Perltidy contains a number of rules which help avoid known subtleties and problems with older versions of perl, and these rules always take priority over whatever formatting flags have been set. For example, perltidy will usually avoid starting a new line with a bareword, because this might cause problems if <code>use strict</code> is active.

There is no way to override these rules.

</dd>
</dl>

<h1 id="HTML-OPTIONS">HTML OPTIONS</h1>

<dl>

<dt id="The--html-master-switch">The -html master switch</dt>
<dd>

The flag -html causes perltidy to write an html file with extension .html. So, for example, the following command

<pre><code> perltidy -html somefile.pl</code></pre>

will produce a syntax-colored html file named somefile.pl.html which may be viewed with a browser.

Please Note: In this case, perltidy does not do any formatting to the input file, and it does not write a formatted file with extension .tdy. This means that two perltidy runs are required to create a fully reformatted, html copy of a script.

</dd>
<dt id="The--pre-flag-for-code-snippets">The -pre flag for code snippets</dt>
<dd>

When the -pre flag is given, only the pre-formatted section, within the &lt;PRE&gt; and &lt;/PRE&gt; tags, will be output. This simplifies inclusion of the output in other files. The default is to output a complete web page.

</dd>
<dt id="The--nnn-flag-for-line-numbering">The -nnn flag for line numbering</dt>
<dd>

When the -nnn flag is given, the output lines will be numbered.

</dd>
<dt id="The--toc-or---html-table-of-contents-flag">The -toc, or --html-table-of-contents flag</dt>
<dd>

By default, a table of contents to packages and subroutines will be written at the start of html output. Use -ntoc to prevent this. This might be useful, for example, for a pod document which contains a number of unrelated code snippets. This flag only influences the code table of contents; it has no effect on any table of contents produced by pod2html (see next item).

</dd>
<dt id="The--pod-or---pod2html-flag">The -pod, or --pod2html flag</dt>
<dd>

There are two options for formatting pod documentation. The default is to pass the pod through the Pod::Html module (which forms the basis of the pod2html utility). Any code sections are formatted by perltidy, and the results then merged. Note: perltidy creates a temporary file when Pod::Html is used; see <a href="#FILES">&quot;FILES&quot;</a>. Also, Pod::Html creates temporary files for its cache.

NOTE: Perltidy counts the number of <code>=cut</code> lines, and either moves the pod text to the top of the html file if there is one <code>=cut</code>, or leaves the pod text in its original order (interleaved with code) otherwise.

Most of the flags accepted by pod2html may be included in the perltidy command line, and they will be passed to pod2html. In some cases, the flags have a prefix <code>pod</code> to emphasize that they are for the pod2html, and this prefix will be removed before they are passed to pod2html. The flags which have the additional <code>pod</code> prefix are:

<pre><code> --[no]podheader --[no]podindex --[no]podrecurse --[no]podquiet 
 --[no]podverbose --podflush</code></pre>

The flags which are unchanged from their use in pod2html are:

<pre><code> --backlink=s --cachedir=s --htmlroot=s --libpods=s --title=s
 --podpath=s --podroot=s </code></pre>

where &#39;s&#39; is an appropriate character string. Not all of these flags are available in older versions of Pod::Html. See your Pod::Html documentation for more information.

The alternative, indicated with -npod, is not to use Pod::Html, but rather to format pod text in italics (or whatever the stylesheet indicates), without special html markup. This is useful, for example, if pod is being used as an alternative way to write comments.

</dd>
<dt id="The--frm-or---frames-flag">The -frm, or --frames flag</dt>
<dd>

By default, a single html output file is produced. This can be changed with the -frm option, which creates a frame holding a table of contents in the left panel and the source code in the right side. This simplifies code browsing. Assume, for example, that the input file is MyModule.pm. Then, for default file extension choices, these three files will be created:

<pre><code> MyModule.pm.html - the frame
 MyModule.pm.toc.html - the table of contents
 MyModule.pm.src.html - the formatted source code</code></pre>

Obviously this file naming scheme requires that output be directed to a real file (as opposed to, say, standard output). If this is not the case, or if the file extension is unknown, the -frm option will be ignored.

</dd>
<dt id="The--text-s-or---html-toc-extension-flag">The -text=s, or --html-toc-extension flag</dt>
<dd>

Use this flag to specify the extra file extension of the table of contents file when html frames are used. The default is &quot;toc&quot;. See <a href="#Specifying-File-Extensions">&quot;Specifying File Extensions&quot;</a>.

</dd>
<dt id="The--sext-s-or---html-src-extension-flag">The -sext=s, or --html-src-extension flag</dt>
<dd>

Use this flag to specify the extra file extension of the content file when html frames are used. The default is &quot;src&quot;. See <a href="#Specifying-File-Extensions">&quot;Specifying File Extensions&quot;</a>.

</dd>
<dt id="The--hent-or---html-entities-flag">The -hent, or --html-entities flag</dt>
<dd>

This flag controls the use of Html::Entities for html formatting. By default, the module Html::Entities is used to encode special symbols. This may not be the right thing for some browser/language combinations. Use --nohtml-entities or -nhent to prevent this.

</dd>
<dt id="Style-Sheets">Style Sheets</dt>
<dd>

Style sheets make it very convenient to control and adjust the appearance of html pages. The default behavior is to write a page of html with an embedded style sheet.

An alternative to an embedded style sheet is to create a page with a link to an external style sheet. This is indicated with the -css=filename, where the external style sheet is filename. The external style sheet filename will be created if and only if it does not exist. This option is useful for controlling multiple pages from a single style sheet.

To cause perltidy to write a style sheet to standard output and exit, use the -ss, or --stylesheet, flag. This is useful if the style sheet could not be written for some reason, such as if the -pre flag was used. Thus, for example,

<pre><code> perltidy -html -ss &gt;mystyle.css</code></pre>

will write a style sheet with the default properties to file mystyle.css.

The use of style sheets is encouraged, but a web page without a style sheets can be created with the flag -nss. Use this option if you must to be sure that older browsers (roughly speaking, versions prior to 4.0 of Netscape Navigator and Internet Explorer) can display the syntax-coloring of the html files.

</dd>
<dt id="Controlling-HTML-properties">Controlling HTML properties</dt>
<dd>

Note: It is usually more convenient to accept the default properties and then edit the stylesheet which is produced. However, this section shows how to control the properties with flags to perltidy.

Syntax colors may be changed from their default values by flags of the either the long form, -html-color-xxxxxx=n, or more conveniently the short form, -hcx=n, where xxxxxx is one of the following words, and x is the corresponding abbreviation:

<pre><code> Token Type xxxxxx x 
 ---------- -------- --
 comment comment c
 number numeric n
 identifier identifier i
 bareword, function bareword w
 keyword keyword k
 quite, pattern quote q
 here doc text here-doc-text h
 here doc target here-doc-target hh
 punctuation punctuation pu
 parentheses paren p
 structural braces structure s
 semicolon semicolon sc
 colon colon co
 comma comma cm
 label label j
 sub definition name subroutine m
 pod text pod-text pd</code></pre>

A default set of colors has been defined, but they may be changed by providing values to any of the following parameters, where n is either a 6 digit hex RGB color value or an ascii name for a color, such as &#39;red&#39;.

To illustrate, the following command will produce an html file somefile.pl.html with &quot;aqua&quot; keywords:

<pre><code> perltidy -html -hck=00ffff somefile.pl</code></pre>

and this should be equivalent for most browsers:

<pre><code> perltidy -html -hck=aqua somefile.pl</code></pre>

Perltidy merely writes any non-hex names that it sees in the html file. The following 16 color names are defined in the HTML 3.2 standard:

<pre><code> black =&gt; 000000,
 silver =&gt; c0c0c0,
 gray =&gt; 808080,
 white =&gt; ffffff,
 maroon =&gt; 800000,
 red =&gt; ff0000,
 purple =&gt; 800080,
 fuchsia =&gt; ff00ff,
 green =&gt; 008000,
 lime =&gt; 00ff00,
 olive =&gt; 808000,
 yellow =&gt; ffff00
 navy =&gt; 000080,
 blue =&gt; 0000ff,
 teal =&gt; 008080,
 aqua =&gt; 00ffff,</code></pre>

Many more names are supported in specific browsers, but it is safest to use the hex codes for other colors. Helpful color tables can be located with an internet search for &quot;HTML color tables&quot;.

Besides color, two other character attributes may be set: bold, and italics. To set a token type to use bold, use the flag --html-bold-xxxxxx or -hbx, where xxxxxx or x are the long or short names from the above table. Conversely, to set a token type to NOT use bold, use --nohtml-bold-xxxxxx or -nhbx.

Likewise, to set a token type to use an italic font, use the flag --html-italic-xxxxxx or -hix, where again xxxxxx or x are the long or short names from the above table. And to set a token type to NOT use italics, use --nohtml-italic-xxxxxx or -nhix.

For example, to use bold braces and lime color, non-bold, italics keywords the following command would be used:

<pre><code> perltidy -html -hbs -hck=00FF00 -nhbk -hik somefile.pl</code></pre>

The background color can be specified with --html-color-background=n, or -hcbg=n for short, where n is a 6 character hex RGB value. The default color of text is the value given to punctuation, which is black as a default.

Here are some notes and hints:

1. If you find a preferred set of these parameters, you may want to create a .perltidyrc file containing them. See the perltidy man page for an explanation.

2. Rather than specifying values for these parameters, it is probably easier to accept the defaults and then edit a style sheet. The style sheet contains comments which should make this easy.

3. The syntax-colored html files can be very large, so it may be best to split large files into smaller pieces to improve download times.

</dd>
</dl>

<h1 id="SOME-COMMON-INPUT-CONVENTIONS">SOME COMMON INPUT CONVENTIONS</h1>

<h2 id="Specifying-Block-Types">Specifying Block Types</h2>

Several parameters which refer to code block types may be customized by also specifying an associated list of block types. The type of a block is the name of the keyword which introduces that block, such as if, else, or sub. An exception is a labeled block, which has no keyword, and should be specified with just a colon. To specify all blocks use &#39;*&#39;.

The keyword sub indicates a named sub. For anonymous subs, use the special keyword asub.

For example, the following parameter specifies <code>sub</code>, labels, <code>BEGIN</code>, and <code>END</code> blocks:

<pre><code> -cscl=&quot;sub : BEGIN END&quot;</code></pre>

(the meaning of the -cscl parameter is described above.) Note that quotes are required around the list of block types because of the spaces. For another example, the following list specifies all block types for vertical tightness:

<pre><code> -bbvtl=&#39;*&#39;</code></pre>

<h2 id="Specifying-File-Extensions">Specifying File Extensions</h2>

Several parameters allow default file extensions to be overridden. For example, a backup file extension may be specified with -bext=ext, where ext is some new extension. In order to provides the user some flexibility, the following convention is used in all cases to decide if a leading &#39;.&#39; should be used. If the extension <code>ext</code> begins with <code>A-Z</code>, <code>a-z</code>, or <code>0-9</code>, then it will be appended to the filename with an intermediate &#39;.&#39; (or perhaps a &#39;_&#39; on VMS systems). Otherwise, it will be appended directly.

For example, suppose the file is somefile.pl. For <code>-bext=old</code>, a &#39;.&#39; is added to give somefile.pl.old. For <code>-bext=.old</code>, no additional &#39;.&#39; is added, so again the backup file is somefile.pl.old. For <code>-bext=~</code>, then no dot is added, and the backup file will be somefile.pl~ .

<h1 id="SWITCHES-WHICH-MAY-BE-NEGATED">SWITCHES WHICH MAY BE NEGATED</h1>

The following list shows all short parameter names which allow a prefix &#39;n&#39; to produce the negated form:

Equivalently, the prefix &#39;no&#39; or &#39;no-&#39; on the corresponding long names may be used.

<h1 id="LIMITATIONS">LIMITATIONS</h1>

<dl>

<dt id="Parsing-Limitations">Parsing Limitations</dt>
<dd>

Perltidy should work properly on most perl scripts. It does a lot of self-checking, but still, it is possible that an error could be introduced and go undetected. Therefore, it is essential to make careful backups and to test reformatted scripts.

The main current limitation is that perltidy does not scan modules included with &#39;use&#39; statements. This makes it necessary to guess the context of any bare words introduced by such modules. Perltidy has good guessing algorithms, but they are not infallible. When it must guess, it leaves a message in the log file.

If you encounter a bug, please report it.

</dd>
<dt id="What-perltidy-does-not-parse-and-format">What perltidy does not parse and format</dt>
<dd>

Perltidy indents but does not reformat comments and <code>qw</code> quotes. Perltidy does not in any way modify the contents of here documents or quoted text, even if they contain source code. (You could, however, reformat them separately). Perltidy does not format &#39;format&#39; sections in any way. And, of course, it does not modify pod documents.

</dd>
</dl>

<h1 id="FILES">FILES</h1>

<dl>

<dt id="Temporary-files">Temporary files</dt>
<dd>

Under the -html option with the default --pod2html flag, a temporary file is required to pass text to Pod::Html. Unix systems will try to use the POSIX tmpnam() function. Otherwise the file perltidy.TMP will be temporarily created in the current working directory.

</dd>
<dt id="Special-files-when-standard-input-is-used">Special files when standard input is used</dt>
<dd>

When standard input is used, the log file, if saved, is perltidy.LOG, and any errors are written to perltidy.ERR unless the -se flag is set. These are saved in the current working directory.

</dd>
<dt id="Files-overwritten">Files overwritten</dt>
<dd>

The following file extensions are used by perltidy, and files with these extensions may be overwritten or deleted: .ERR, .LOG, .TEE, and/or .tdy, .html, and .bak, depending on the run type and settings.

</dd>
<dt id="Files-extensions-limitations">Files extensions limitations</dt>
<dd>

Perltidy does not operate on files for which the run could produce a file with a duplicated file extension. These extensions include .LOG, .ERR, .TEE, and perhaps .tdy and .bak, depending on the run type. The purpose of this rule is to prevent generating confusing filenames such as somefile.tdy.tdy.tdy.

</dd>
</dl>

<h1 id="ERROR-HANDLING">ERROR HANDLING</h1>

An exit value of 0, 1, or 2 is returned by perltidy to indicate the status of the result.

A exit value of 0 indicates that perltidy ran to completion with no error messages.

A non-zero exit value indicates some kind of problem was detected.

An exit value of 1 indicates that perltidy terminated prematurely, usually due to some kind of errors in the input parameters. This can happen for example if a parameter is misspelled or given an invalid value. Error messages in the standard error output will indicate the cause of any problem. If perltidy terminates prematurely then no output files will be produced.

An exit value of 2 indicates that perltidy was able to run to completion but there there are (1) warning messages in the standard error output related to parameter errors or problems and/or (2) warning messages in the perltidy error file(s) relating to possible syntax errors in one or more of the source script(s) being tidied. When multiple files are being processed, an error detected in any single file will produce this type of exit condition.

perlstyle(1), Perl::Tidy(3)

<h1 id="INSTALLATION">INSTALLATION</h1>

The perltidy binary uses the Perl::Tidy module and is installed when that module is installed. The module name is case-sensitive. For example, the basic command for installing with cpanm is &#39;cpanm Perl::Tidy&#39;.

<h1 id="VERSION">VERSION</h1>

This man page documents perltidy version 20210111

<h1 id="BUG-REPORTS">BUG REPORTS</h1>

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>

To report a new bug or problem, use the link on this page.

The source code repository is at <a href="https://github.com/perltidy/perltidy">https://github.com/perltidy/perltidy</a>.

<h1 id="COPYRIGHT">COPYRIGHT</h1>

<h1 id="LICENSE">LICENSE</h1>

This package is free software; you can redistribute it and/or modify it under the terms of the &quot;GNU General Public License&quot;.

Please refer to the file &quot;COPYING&quot; for details.

<h1 id="DISCLAIMER">DISCLAIMER</h1>

This package is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

See the &quot;GNU General Public License&quot; for more details.

</body>

</html>

Cancel