.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.32
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.TH PERLFORM 1 "2006-01-07" "perl v5.8.8" "Perl Programmers Reference Guide"
.IX Xref "format report chart"
Perl has a mechanism to help you generate simple reports and charts. To
facilitate this, Perl helps you code up your output page close to how it
will look when it's printed. It can keep track of things like how many
lines are on a page, what page you're on, when to print page headers,
etc. Keywords are borrowed from \s-1FORTRAN:\s0 \fIformat()\fR to declare and \fIwrite()\fR
to execute; see their entries in perlfunc. Fortunately, the layout is
much more legible, more like \s-1BASIC\s0's \s-1PRINT\s0 \s-1USING\s0 statement. Think of it
as a poor man's \fInroff\fR\|(1).
Formats, like packages and subroutines, are declared rather than
executed, so they may occur at any point in your program. (Usually it's
best to keep them all together though.) They have their own namespace
apart from all the other \*(L"types\*(R" in Perl. This means that if you have a
function named \*(L"Foo\*(R", it is not the same thing as having a format named
\&\*(L"Foo\*(R". However, the default name for the format associated with a given
filehandle is the same as the name of the filehandle. Thus, the default
format for \s-1STDOUT\s0 is named \*(L"\s-1STDOUT\s0\*(R", and the default format for filehandle
\&\s-1TEMP\s0 is named \*(L"\s-1TEMP\s0\*(R". They just look the same. They aren't.
Output record formats are declared as follows:
If the name is omitted, format \*(L"\s-1STDOUT\s0\*(R" is defined. A single \*(L".\*(R" in
column 1 is used to terminate a format. \s-1FORMLIST\s0 consists of a sequence
of lines, each of which may be one of three types:
A comment, indicated by putting a '#' in the first column.
A \*(L"picture\*(R" line giving the format for one output line.
An argument line supplying values to plug into the previous picture line.
Picture lines contain output field definitions, intermingled with
literal text. These lines do not undergo any kind of variable interpolation.
Field definitions are made up from a set of characters, for starting and
extending a field to its desired width. This is the complete set of
characters for field definitions:
.IX Xref "format, picture line @ ^ < | > # 0 . ... @* ^* ~ ~~"
\& @ start of regular field
\& ^ start of special field
\& < pad character for left adjustification
\& | pad character for centering
\& > pad character for right adjustificat
\& # pad character for a right justified numeric field
\& 0 instead of first #: pad number with leading zeroes
\& . decimal point within a numeric field
\& ... terminate a text field, show "..." as truncation evidence
\& @* variable width field for a multi-line value
\& ^* variable width field for next line of a multi-line value
\& ~ suppress line with all fields empty
\& ~~ repeat line until all fields are exhausted
Each field in a picture line starts with either \*(L"@\*(R" (at) or \*(L"^\*(R" (caret),
indicating what we'll call, respectively, a \*(L"regular\*(R" or \*(L"special\*(R" field.
The choice of pad characters determines whether a field is textual or
numeric. The tilde operators are not part of a field. Let's look at
the various possibilities in detail.
.IX Xref "format, text field"
.IX Subsection "Text Fields"
The length of the field is supplied by padding out the field with multiple
"<\*(L", \*(R">\*(L", or \*(R"|\*(L" characters to specify a non-numeric field with,
respectively, left justification, right justification, or centering.
For a regular field, the value (up to the first newline) is taken and
printed according to the selected justification, truncating excess characters.
If you terminate a text field with \*(R"...", three dots will be shown if
the value is truncated. A special text field may be used to do rudimentary
multi-line text block filling; see \*(L"Using Fill Mode\*(R" for details.
\& @<<<<<< @|||||| @>>>>>>
\& "left", "middle", "right"
.IX Xref "# format, numeric field"
.IX Subsection "Numeric Fields"
Using \*(L"#\*(R" as a padding character specifies a numeric field, with
right justification. An optional \*(L".\*(R" defines the position of the
decimal point. With a \*(L"0\*(R" (zero) instead of the first \*(L"#\*(R", the
formatted number will be padded with leading zeroes if necessary.
A special numeric field is blanked out if the value is undefined.
If the resulting value would exceed the width specified the field is
filled with \*(L"#\*(R" as overflow evidence.
\& @### @.### @##.### @### @### ^####
\& 42, 3.1415, undef, 0, 10000, undef
.Sh "The Field @* for Variable Width Multi-Line Text"
.IX Subsection "The Field @* for Variable Width Multi-Line Text"
The field \*(L"@*\*(R" can be used for printing multi\-line, nontruncated
values; it should (but need not) appear by itself on a line. A final
line feed is chomped off, but all other characters are emitted verbatim.
.Sh "The Field ^* for Variable Width One-line-at-a-time Text"
.IX Subsection "The Field ^* for Variable Width One-line-at-a-time Text"
Like \*(L"@*\*(R", this is a variable width field. The value supplied must be a
scalar variable. Perl puts the first line (up to the first \*(L"\en\*(R") of the
text into the field, and then chops off the front of the string so that
the next time the variable is referenced, more of the text can be printed.
The variable will \fInot\fR be restored.
\& $text = "line 1\enline 2\enline 3";
.IX Xref "format, specifying values"
.IX Subsection "Specifying Values"
The values are specified on the following format line in the same order as
the picture fields. The expressions providing the values must be
separated by commas. They are all evaluated in a list context
before the line is processed, so a single list expression could produce
multiple list elements. The expressions may be spread out to more than
one line if enclosed in braces. If so, the opening brace must be the first
token on the first line. If an expression evaluates to a number with a
decimal part, and if the corresponding picture specifies that the decimal
part should appear in the output (that is, any picture except multiple \*(L"#\*(R"
characters \fBwithout\fR an embedded \*(L".\*(R"), the character used for the decimal
point is \fBalways\fR determined by the current \s-1LC_NUMERIC\s0 locale. This
means that, if, for example, the run-time environment happens to specify a
German locale, \*(L",\*(R" will be used instead of the default \*(L".\*(R". See
perllocale and \*(L"\s-1WARNINGS\s0\*(R" for more information.
.IX Xref "format, fill mode"
.IX Subsection "Using Fill Mode"
On text fields the caret enables a kind of fill mode. Instead of an
arbitrary expression, the value supplied must be a scalar variable
that contains a text string. Perl puts the next portion of the text into
the field, and then chops off the front of the string so that the next time
the variable is referenced, more of the text can be printed. (Yes, this
means that the variable itself is altered during execution of the \fIwrite()\fR
call, and is not restored.) The next portion of text is determined by
a crude line breaking algorithm. You may use the carriage return character
(\f(CW\*(C`\er\*(C'\fR) to force a line break. You can change which characters are legal
to break on by changing the variable \f(CW$:\fR (that's
\&\f(CW$FORMAT_LINE_BREAK_CHARACTERS\fR if you're using the English module) to a
list of the desired characters.
Normally you would use a sequence of fields in a vertical stack associated
with the same scalar variable to print out a block of text. You might wish
to end the final field with the text \*(L"...\*(R", which will appear in the output
if the text was too long to appear in its entirety.
.Sh "Suppressing Lines Where All Fields Are Void"
.IX Xref "format, suppressing lines"
.IX Subsection "Suppressing Lines Where All Fields Are Void"
Using caret fields can produce lines where all fields are blank. You can
suppress such lines by putting a \*(L"~\*(R" (tilde) character anywhere in the
line. The tilde will be translated to a space upon output.
.Sh "Repeating Format Lines"
.IX Xref "format, repeating lines"
.IX Subsection "Repeating Format Lines"
If you put two contiguous tilde characters \*(L"~~\*(R" anywhere into a line,
the line will be repeated until all the fields on the line are exhausted,
i.e. undefined. For special (caret) text fields this will occur sooner or
later, but if you use a text field of the at variety, the expression you
supply had better not give the same value every time forever! (\f(CW\*(C`shift(@f)\*(C'\fR
is a simple example that would work.) Don't use a regular (at) numeric
field in such lines, because it will never go blank.
.Sh "Top of Form Processing"
.IX Xref "format, top of form top header"
.IX Subsection "Top of Form Processing"
Top-of-form processing is by default handled by a format with the
same name as the current filehandle with \*(L"_TOP\*(R" concatenated to it.
It's triggered at the top of each page. See \*(L"write\*(R" in perlfunc.
\& # a report on the /etc/passwd file
\& Name Login Office Uid Gid Home
\& ------------------------------------------------------------------
\& @<<<<<<<<<<<<<<<<<< @||||||| @<<<<<<@>>>> @>>>> @<<<<<<<<<<<<<<<<<
\& $name, $login, $office,$uid,$gid, $home
\& # a report from a bug report form
\& @<<<<<<<<<<<<<<<<<<<<<<< @||| @>>>>>>>>>>>>>>>>>>>>>>>
\& ------------------------------------------------------------------
\& Subject: @<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& Index: @<<<<<<<<<<<<<<<<<<<<<<<<<<<< ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& Priority: @<<<<<<<<<< Date: @<<<<<<< ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& $priority, $date, $description
\& From: @<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& Assigned to: @<<<<<<<<<<<<<<<<<<<<<< ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& $programmer, $description
\& ~ ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& ~ ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& ~ ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& ~ ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& ~ ^<<<<<<<<<<<<<<<<<<<<<<<...
It is possible to intermix \fIprint()\fRs with \fIwrite()\fRs on the same output
channel, but you'll have to handle \f(CW\*(C`$\-\*(C'\fR (\f(CW$FORMAT_LINES_LEFT\fR)
.IX Xref "format variables format, variables"
.IX Subsection "Format Variables"
The current format name is stored in the variable \f(CW$~\fR (\f(CW$FORMAT_NAME\fR),
and the current top of form format name is in \f(CW$^\fR (\f(CW$FORMAT_TOP_NAME\fR).
The current output page number is stored in \f(CW$%\fR (\f(CW$FORMAT_PAGE_NUMBER\fR),
and the number of lines on the page is in \f(CW$=\fR (\f(CW$FORMAT_LINES_PER_PAGE\fR).
Whether to autoflush output on this handle is stored in \f(CW$|\fR
(\f(CW$OUTPUT_AUTOFLUSH\fR). The string output before each top of page (except
the first) is stored in \f(CW$^L\fR (\f(CW$FORMAT_FORMFEED\fR). These variables are
set on a per-filehandle basis, so you'll need to \fIselect()\fR into a different
\& $~ = "My_Other_Format",
Pretty ugly, eh? It's a common idiom though, so don't be too surprised
when you see it. You can at least use a temporary variable to hold
the previous filehandle: (this is a much better approach in general,
because not only does legibility improve, you now have intermediary
stage in the expression to single-step the debugger through):
\& $~ = "My_Other_Format";
If you use the English module, you can even read the variable names:
\& use English '-no_match_vars';
\& $FORMAT_NAME = "My_Other_Format";
\& $FORMAT_TOP_NAME = "My_Top_Format";
But you still have those funny \fIselect()\fRs. So just use the FileHandle
module. Now, you can access these special variables using lowercase
\& format_name OUTF "My_Other_Format";
\& format_top_name OUTF "My_Top_Format";
Because the values line may contain arbitrary expressions (for at fields,
not caret fields), you can farm out more sophisticated processing
to other functions, like \fIsprintf()\fR or one of your own. For example:
To get a real at or caret into the field, do this:
To center a whole line of text, do something like this:
\& @|||||||||||||||||||||||||||||||||||||||||||||||
There is no builtin way to say \*(L"float this to the right hand side
of the page, however wide it is.\*(R" You have to specify where it goes.
The truly desperate can generate their own format on the fly, based
on the current number of columns, and then \fIeval()\fR it:
\& $format = "format STDOUT = \en"
\& . '^' . '<' x $cols . "\en"
\& . "\et^" . "<" x ($cols-8) . "~~\en"
\& print $format if $Debugging;
Which would generate a format looking something like this:
\& ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
\& ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<~~
Here's a little program that's somewhat like \fIfmt\fR\|(1):
\& ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~
.IX Xref "format, footer footer"
While \f(CW$FORMAT_TOP_NAME\fR contains the name of the current header format,
there is no corresponding mechanism to automatically do the same thing
for a footer. Not knowing how big a format is going to be until you
evaluate it is one of the major problems. It's on the \s-1TODO\s0 list.
Here's one strategy: If you have a fixed-size footer, you can get footers
by checking \f(CW$FORMAT_LINES_LEFT\fR before each \fIwrite()\fR and print the footer
Here's another strategy: Open a pipe to yourself, using \f(CW\*(C`open(MYSELF, "|\-")\*(C'\fR
(see \*(L"\fIopen()\fR\*(R" in perlfunc) and always \fIwrite()\fR to \s-1MYSELF\s0 instead of \s-1STDOUT\s0.
Have your child process massage its \s-1STDIN\s0 to rearrange headers and footers
however you like. Not very convenient, but doable.
.Sh "Accessing Formatting Internals"
.IX Xref "format, internals"
.IX Subsection "Accessing Formatting Internals"
For low-level access to the formatting mechanism. you may use \fIformline()\fR
and access \f(CW$^A\fR (the \f(CW$ACCUMULATOR\fR variable) directly.
\& $str = formline <<'END', 1,2,3;
\& print "Wow, I just stored `$^A' in the accumulator!\en";
Or to make an \fIswrite()\fR subroutine, which is to \fIwrite()\fR what \fIsprintf()\fR
is to \fIprintf()\fR, do this:
\& croak "usage: swrite PICTURE ARGS" unless @_;
\& $string = swrite(<<'END', 1, 2, 3);
The lone dot that ends a format can also prematurely end a mail
message passing through a misconfigured Internet mailer (and based on
experience, such misconfiguration is the rule, not the exception). So
when sending format code through mail, you should indent it so that
the format-ending dot is not on the left margin; this will prevent
Lexical variables (declared with \*(L"my\*(R") are not visible within a
format unless the format is declared within the scope of the lexical
variable. (They weren't visible at all before version 5.001.)
Formats are the only part of Perl that unconditionally use information
from a program's locale; if a program's environment specifies an
\&\s-1LC_NUMERIC\s0 locale, it is always used to specify the decimal point
character in formatted output. Perl ignores all other aspects of locale
handling unless the \f(CW\*(C`use locale\*(C'\fR pragma is in effect. Formatted output
cannot be controlled by \f(CW\*(C`use locale\*(C'\fR because the pragma is tied to the
block structure of the program, and, for historical reasons, formats
exist outside that block structure. See perllocale for further
discussion of locale handling.
Within strings that are to be displayed in a fixed length text field,
each control character is substituted by a space. (But remember the
special meaning of \f(CW\*(C`\er\*(C'\fR when using fill mode.) This is done to avoid
misalignment when control characters \*(L"disappear\*(R" on some output media.
projects / OpenSPARC-T2-SAM / blob