![]() perltidy -i=3 Įxecute perltidy on file, with 3 columns for each level of indentation ( -i=3) instead of the default 4 columns. perltidy -gnu Įxecute perltidy on file with a style which approximates the GNU Coding Standards for C programs. Same as the previous example except that the backup files .bak and .bak will be deleted if there are no errors. If .bak and/or .bak already exist, they will be overwritten. ![]() ![]() Modify and in place, and backup the originals to .bak and .bak. For any file with an error, there will be a file with extension. The output will be in files with an appended. pl files in the current directory with the default options. This will produce a file .tdy containing the script reformatted using the default options, which approximate the style suggested in perlstyle(1). When the -html flag is given, the output is passed through an HTML formatter which is described in "HTML OPTIONS". 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 "FORMATTING OPTIONS". Without this flag, the output is passed through a formatter. Perltidy can produce output on either of two modes, depending on the existence of an -html flag. New users may benefit from the short tutorial which can be found at Ī convenient aid to systematically defining a set of style parameters can be found at Many users will find enough information in "EXAMPLES" to get started. It is the file Perl::Tidy.pod in the source distribution. ![]() ![]() For documentation describing how to call the Perl::Tidy module from other applications see the separate documentation for Perl::Tidy. Perltidy is a commandline frontend to the module Perl::Tidy. This document describes the parameters available for controlling this formatting. Perltidy reads a perl script and writes an indented, reformatted script. (output goes to file1.tdy, file2.tdy, file3.tdy. Perltidy - a perl script indenter and reformatter SYNOPSIS perltidy file1 file2 file3. Retaining or Ignoring Existing Line Breaks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |