Gecko [ nbspublicschool.com ]

Name	Size	Permission
App::cpanminus.3pm	14.28 KB	-r--r--r--
App::cpanminus::fatscript.3pm	26.28 KB	-r--r--r--
Bundle::DBD::mysql.3pm	4.09 KB	-r--r--r--
CPAN::Meta::Requirements.3pm	13.78 KB	-r--r--r--
CPAN::Meta::YAML.3pm	5.89 KB	-r--r--r--
Canary::Stability.3pm	5.84 KB	-r--r--r--
DBD::mysql.3pm	48.68 KB	-r--r--r--
DBD::mysql::INSTALL.3pm	30.13 KB	-r--r--r--
Data::Dump.3pm	10.51 KB	-r--r--r--
Data::Dump::Filtered.3pm	10.39 KB	-r--r--r--
Data::Dump::Trace.3pm	9 KB	-r--r--r--
Data::Validate::IP.3pm	15.68 KB	-r--r--r--
Devel::CheckLib.3pm	11.45 KB	-r--r--r--
Digest::MD5.3pm	16.16 KB	-r--r--r--
Error.3pm	21.39 KB	-r--r--r--
Error::Simple.3pm	8.15 KB	-r--r--r--
Expect.3pm	60.58 KB	-r--r--r--
Exporter.3pm	22.74 KB	-r--r--r--
Exporter::Heavy.3pm	4.1 KB	-r--r--r--
File::Copy::Recursive.3pm	18.63 KB	-r--r--r--
File::LckPwdF.3pm	11.21 KB	-r--r--r--
File::Path.3pm	32.74 KB	-r--r--r--
File::ReadBackwards.3pm	10.38 KB	-r--r--r--
File::Temp.3pm	39.49 KB	-r--r--r--
HTML::TagParser.3pm	14.01 KB	-r--r--r--
HTTP::Date.3pm	9.36 KB	-r--r--r--
HTTP::Tiny.3pm	29.24 KB	-r--r--r--
IO::AtomicFile.3pm	7.02 KB	-r--r--r--
IO::InnerFile.3pm	7.66 KB	-r--r--r--
IO::Lines.3pm	5.46 KB	-r--r--r--
IO::Pty.3pm	10.14 KB	-r--r--r--
IO::Scalar.3pm	12.19 KB	-r--r--r--
IO::ScalarArray.3pm	12.04 KB	-r--r--r--
IO::Stringy.3pm	5.72 KB	-r--r--r--
IO::Tty.3pm	9.91 KB	-r--r--r--
IO::Tty::Constant.3pm	11.25 KB	-r--r--r--
IO::Wrap.3pm	12.18 KB	-r--r--r--
IO::WrapTie.3pm	16.4 KB	-r--r--r--
JSON.3pm	64.46 KB	-r--r--r--
JSON::Syck.3pm	9.67 KB	-r--r--r--
JSON::XS.3pm	88.67 KB	-r--r--r--
JSON::XS::Boolean.3pm	4.55 KB	-r--r--r--
JSON::backportPP.3pm	65.09 KB	-r--r--r--
JSON::backportPP::Boolean.3pm	4.52 KB	-r--r--r--
JSON::backportPP::Compat5005.3...	4.39 KB	-r--r--r--
JSON::backportPP::Compat5006.3...	4.39 KB	-r--r--r--
Mail::RFC822::Address.3pm	7.11 KB	-r--r--r--
Mock::Config.3pm	7.73 KB	-r--r--r--
Module::Load.3pm	11.18 KB	-r--r--r--
Module::Load::Conditional.3pm	14.24 KB	-r--r--r--
NetAddr::IP.3pm	38.15 KB	-r--r--r--
NetAddr::IP::InetBase.3pm	14.65 KB	-r--r--r--
NetAddr::IP::Lite.3pm	26.89 KB	-r--r--r--
NetAddr::IP::Util.3pm	23.49 KB	-r--r--r--
NetAddr::IP::UtilPP.3pm	11.04 KB	-r--r--r--
POD2::DE::local::lib.3pm	24.23 KB	-r--r--r--
POD2::PT_BR::local::lib.3pm	24.62 KB	-r--r--r--
Path::Tiny.3pm	52.88 KB	-r--r--r--
Storable.3pm	45.41 KB	-r--r--r--
Template::Toolkit::Simple.3pm	13.37 KB	-r--r--r--
Test2.3pm	11.13 KB	-r--r--r--
Test2::API.3pm	37.22 KB	-r--r--r--
Test2::API::Breakage.3pm	6.63 KB	-r--r--r--
Test2::API::Context.3pm	25.52 KB	-r--r--r--
Test2::API::Instance.3pm	14.72 KB	-r--r--r--
Test2::API::InterceptResult.3p...	22 KB	-r--r--r--
Test2::API::InterceptResult::E...	26.72 KB	-r--r--r--
Test2::API::InterceptResult::H...	4.64 KB	-r--r--r--
Test2::API::InterceptResult::S...	4.77 KB	-r--r--r--
Test2::API::Stack.3pm	8.18 KB	-r--r--r--
Test2::Event.3pm	22.81 KB	-r--r--r--
Test2::Event::Bail.3pm	5.15 KB	-r--r--r--
Test2::Event::Diag.3pm	5.02 KB	-r--r--r--
Test2::Event::Encoding.3pm	5.36 KB	-r--r--r--
Test2::Event::Exception.3pm	5.3 KB	-r--r--r--
Test2::Event::Fail.3pm	4.93 KB	-r--r--r--
Test2::Event::Generic.3pm	9.66 KB	-r--r--r--
Test2::Event::Note.3pm	5.01 KB	-r--r--r--
Test2::Event::Ok.3pm	5.69 KB	-r--r--r--
Test2::Event::Pass.3pm	4.93 KB	-r--r--r--
Test2::Event::Plan.3pm	5.58 KB	-r--r--r--
Test2::Event::Skip.3pm	5.34 KB	-r--r--r--
Test2::Event::Subtest.3pm	5.25 KB	-r--r--r--
Test2::Event::TAP::Version.3pm	5.18 KB	-r--r--r--
Test2::Event::V2.3pm	8.26 KB	-r--r--r--
Test2::Event::Waiting.3pm	4.8 KB	-r--r--r--
Test2::EventFacet.3pm	5.57 KB	-r--r--r--
Test2::EventFacet::About.3pm	6.37 KB	-r--r--r--
Test2::EventFacet::Amnesty.3pm	6.16 KB	-r--r--r--
Test2::EventFacet::Assert.3pm	6.41 KB	-r--r--r--
Test2::EventFacet::Control.3pm	7.4 KB	-r--r--r--
Test2::EventFacet::Error.3pm	6.26 KB	-r--r--r--
Test2::EventFacet::Hub.3pm	7.12 KB	-r--r--r--
Test2::EventFacet::Info.3pm	8.17 KB	-r--r--r--
Test2::EventFacet::Info::Table...	7.16 KB	-r--r--r--
Test2::EventFacet::Meta.3pm	5.22 KB	-r--r--r--
Test2::EventFacet::Parent.3pm	6.31 KB	-r--r--r--
Test2::EventFacet::Plan.3pm	6.67 KB	-r--r--r--
Test2::EventFacet::Render.3pm	6.84 KB	-r--r--r--
Test2::EventFacet::Trace.3pm	12.58 KB	-r--r--r--
Test2::Formatter.3pm	7.9 KB	-r--r--r--
Test2::Formatter::TAP.3pm	6.38 KB	-r--r--r--
Test2::Hub.3pm	18.36 KB	-r--r--r--
Test2::Hub::Interceptor.3pm	4.63 KB	-r--r--r--
Test2::Hub::Interceptor::Termi...	4.67 KB	-r--r--r--
Test2::Hub::Subtest.3pm	5.48 KB	-r--r--r--
Test2::IPC.3pm	5.18 KB	-r--r--r--
Test2::IPC::Driver.3pm	10.51 KB	-r--r--r--
Test2::IPC::Driver::Files.3pm	5.49 KB	-r--r--r--
Test2::Tools::Tiny.3pm	8.45 KB	-r--r--r--
Test2::Transition.3pm	19.71 KB	-r--r--r--
Test2::Util.3pm	9.42 KB	-r--r--r--
Test2::Util::ExternalMeta.3pm	7.22 KB	-r--r--r--
Test2::Util::Facets2Legacy.3pm	9.88 KB	-r--r--r--
Test2::Util::HashBase.3pm	13.91 KB	-r--r--r--
Test2::Util::Trace.3pm	4.74 KB	-r--r--r--
Test::Builder.3pm	28.79 KB	-r--r--r--
Test::Builder::Formatter.3pm	4.85 KB	-r--r--r--
Test::Builder::IO::Scalar.3pm	11.27 KB	-r--r--r--
Test::Builder::Module.3pm	7.35 KB	-r--r--r--
Test::Builder::Tester.3pm	13.04 KB	-r--r--r--
Test::Builder::Tester::Color.3...	4.82 KB	-r--r--r--
Test::Builder::TodoDiag.3pm	4.82 KB	-r--r--r--
Test::Deep.3pm	47.56 KB	-r--r--r--
Test::Deep::NoTest.3pm	4.33 KB	-r--r--r--
Test::Fatal.3pm	10.69 KB	-r--r--r--
Test::File.3pm	23.7 KB	-r--r--r--
Test::More.3pm	43.96 KB	-r--r--r--
Test::Needs.3pm	7.27 KB	-r--r--r--
Test::Requires.3pm	5.93 KB	-r--r--r--
Test::Simple.3pm	10.67 KB	-r--r--r--
Test::Tester.3pm	17.76 KB	-r--r--r--
Test::Tester::Capture.3pm	4.59 KB	-r--r--r--
Test::Tester::CaptureRunner.3p...	4.37 KB	-r--r--r--
Test::Tutorial.3pm	25.46 KB	-r--r--r--
Test::Warnings.3pm	15.7 KB	-r--r--r--
Test::use::ok.3pm	5.52 KB	-r--r--r--
Text::Aligner.3pm	9.77 KB	-r--r--r--
Text::Table.3pm	27.18 KB	-r--r--r--
Time::Local.3pm	15.63 KB	-r--r--r--
Try::Tiny.3pm	22.09 KB	-r--r--r--
URI.3pm	40.31 KB	-r--r--r--
URI::Escape.3pm	9.58 KB	-r--r--r--
URI::Heuristic.3pm	6.84 KB	-r--r--r--
URI::QueryParam.3pm	8.26 KB	-r--r--r--
URI::Split.3pm	5.73 KB	-r--r--r--
URI::URL.3pm	6.19 KB	-r--r--r--
URI::WithBase.3pm	5.91 KB	-r--r--r--
URI::_punycode.3pm	6.32 KB	-r--r--r--
URI::data.3pm	5.98 KB	-r--r--r--
URI::file.3pm	12.16 KB	-r--r--r--
URI::ldap.3pm	7.36 KB	-r--r--r--
YAML::LibYAML.3pm	4.51 KB	-r--r--r--
YAML::Syck.3pm	12.34 KB	-r--r--r--
YAML::XS.3pm	9.57 KB	-r--r--r--
YAML::XS::LibYAML.3pm	3.99 KB	-r--r--r--
lib::core::only.3pm	7.28 KB	-r--r--r--
local::lib.3pm	32.78 KB	-r--r--r--
ok.3pm	4.55 KB	-r--r--r--
version.3pm	15.37 KB	-r--r--r--
version::Internals.3pm	31.34 KB	-r--r--r--

Code Editor : Text::Table.3pm

.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" 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.  \*(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<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    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
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{
.    if \nF \{
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\"
.\" 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
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&
.    ds #] \&
.\}
.    \" simple accents for nroff and troff
.if n \{\
.    ds ' \&
.    ds ` \&
.    ds ^ \&
.    ds , \&
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    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 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
.IX Title "Text::Table 3"
.TH Text::Table 3 "2012-09-23" "perl v5.16.3" "User Contributed Perl Documentation"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "NAME"
Text::Table \- Organize Data in Tables
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
.Vb 11
\&    use Text::Table;
\&    my $tb = Text::Table\->new(
\&        "Planet", "Radius\enkm", "Density\eng/cm^3"
\&    );
\&    $tb\->load(
\&        [ "Mercury", 2360, 3.7 ],
\&        [ "Venus", 6110, 5.1 ],
\&        [ "Earth", 6378, 5.52 ],
\&        [ "Jupiter", 71030, 1.3 ],
\&    );
\&    print $tb;
.Ve
.PP
This prints a table from the given title and data like this:
.PP
.Vb 6
\&  Planet  Radius Density
\&          km     g/cm^3 
\&  Mercury  2360  3.7    
\&  Venus    6110  5.1    
\&  Earth    6378  5.52   
\&  Jupiter 71030  1.3
.Ve
.PP
Note that two-line titles work, and that the planet names are aligned
differently than the numbers.
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
Organization of data in table form is a time-honored and useful
method of data representation.  While columns of data are trivially
generated by computer through formatted output, even simple tasks
like keeping titles aligned with the data columns are not trivial,
and the one-shot solutions one comes up with tend to be particularly
hard to maintain.  Text::Table allows you to create and maintain
tables that adapt to alignment requirements as you use them.
.SS "Overview"
.IX Subsection "Overview"
The process is simple: you create a table (a Text::Table object) by
describing the columns the table is going to have.  Then you load
lines of data into the table, and finally print the resulting output
lines.  Alignment of data and column titles is handled dynamically
in dependence on the data present.
.SS "Table Creation"
.IX Subsection "Table Creation"
In the simplest case, if all you want is a number of (untitled) columns,
you create an unspecified table and start adding data to it.  The number
of columns is taken from the first line of data.
.PP
To specify a table you specify its columns.  A column description
can contain a title and alignment requirements for the data, both
optional.  Additionally, you can specify how the title is aligned with
the body of a column, and how the lines of a multiline title are
aligned among themselves.
.PP
The columns are collected in the table in the
order they are given.  On data entry, each column corresponds to
one data item, and in column selection columns are indexed left to
right, starting from 0.
.PP
Each title can be a multiline string which will be blank-filled to
the length of the longest partial line.  The largest number of title
lines in a column determines how many title lines the table has as a
whole, including the case that no column has any titles.
.PP
On output, Columns are separated by a single blank.  You can control
what goes between columns by specifying separators between (or before,
or after) columns.  Separators don't contain any data and don't count
in column indexing.  They also don't accumulate: in a sequence of only
separators and no columns, only the last one counts.
.SS "Status Information"
.IX Subsection "Status Information"
The width (in characters), height (in lines), number of columns, and
similar data about the table is available.
.SS "Data Loading"
.IX Subsection "Data Loading"
Table data is entered line-wise, each time specifying data entries
for all table columns.  A bulk loader for many lines at once is also
available.  You can clear the data from the table for re-use (though
you will more likely just create another table).
.PP
Data can contain colorizing escape sequences (as provided by
\&\f(CW\*(C`Term::AnsiColor\*(C'\fR) without upsetting the alignment.
.SS "Table Output"
.IX Subsection "Table Output"
The output area of a table is divided in the title and the body.
.PP
The title contains the combined titles from the table columns, if
any.  Its content never changes with a given table, but it may be
spread out differently on the page through alignment with the data.
.PP
The body contains the data lines, aligned column-wise as specified,
and left-aligned with the column title.
.PP
Each of these is arranged like a Perl array (counting from 0) and can
be accessed in portions by specifying a first line and the number
of following lines.  Also like an array, giving a negative first line
counts from the end of the area.  The whole table, the title followed
by the body, can also be accessed in this manner.
.PP
The subdivisions are there so you can repeat the title (or parts of
it) along with parts of the body on output, whether for screen paging
or printout.
.PP
A rule line is also available, which is the horizontal counterpart to
the separator columns you specify with the table.
It is basically a table line as it would appear if all data entries
in the line were empty, that is, a blank line except for where the
column separators have non-blank entries.  If you print it between
data lines, it will not disrupt the vertical separator structure
as a plain blank line would.  You can also request a solid rule
consisting of any character, and even one with the non-blank column
separators replaced by a character of your choice.  This way you can
get the popular representation of line-crossings like so:
.PP
.Vb 3
\&      |
\&  \-\-\-\-+\-\-\-
\&      |
.Ve
.SS "Warning Control"
.IX Subsection "Warning Control"
On table creation, some parameters are checked and warnings issued
if you allow warnings.  You can also turn warnings into fatal errors.
.SH "SPECIFICATIONS"
.IX Header "SPECIFICATIONS"
.SS "Column Specification"
.IX Subsection "Column Specification"
Each column specification is a single scalar.  Columns can be either proper
data columns or column separators.  Both can be specified either as
(possibly multi-line) strings, or in a more explicit form as hash-refs.
In the string form, proper columns are given as plain strings, and
separators are given as scalar references to strings.  In hash form,
separators have a true value in the field \f(CW\*(C`is_sep\*(C'\fR while proper columns
don't have this field.
.IP "Columns as strings" 4
.IX Item "Columns as strings"
A column is given as a column title (any number of lines),
optionally followed by alignment requirements.  Alignment requirements
start with a line that begins with an ampersamd \*(L"&\*(R".  However, only the
last such line counts as such, so if you have title lines that begin
with \*(L"&\*(R", just append an ampersand on a line by itself as a dummy
alignment section if you don't have one anyway.
.Sp
What follows the ampersand on its line is the alignment style (like
\&\fIleft\fR, \fIright\fR, ... as described in \*(L"Alignment\*(R"), you want for
the data in this column.  If nothing follows, the general default \fIauto\fR
is used.  If you specify an invalid alignment style, it falls back to
left alignment.
.Sp
The lines that follow can contain sample data for this column.  These
are considered for alignment in the column, but never actually appear
in the output.  The effect is to guarantee a minimum width for the
column even if the current data doesn't require it.  This helps dampen
the oscillations in the appearance of dynamically aligned tables.
.IP "Columns as Hashes" 4
.IX Item "Columns as Hashes"
The format is
.Sp
.Vb 7
\&    {
\&        title   => $title,
\&        align   => $align,
\&        sample  => $sample,
\&        align_title => $align_title,
\&        align_title_lines => $align_title_lines,
\&    }
.Ve
.Sp
\&\f(CW$title\fR contains the title lines and \f(CW$sample\fR the sample data.  Both can
be given as a string or as an array-ref to the list of lines.  \f(CW$align\fR contains
the alignment style (without a leading ampersand), usually as a string.
You can also give a regular expression here, which specifies regex alignment.
A regex can only be specified in the hash form of a colunm specification.
.Sp
In hash form you can also specify how the title of a column is aligned
with its body.  To do this, you specify the keyword \f(CW\*(C`align_title\*(C'\fR with
\&\f(CW\*(C`left\*(C'\fR, \f(CW\*(C`right\*(C'\fR or \f(CW\*(C`center\*(C'\fR.  Other alignment specifications are not
valid here.  The default is \f(CW\*(C`left\*(C'\fR.
.Sp
\&\f(CW\*(C`align_title\*(C'\fR also specifies how the lines of a multiline title are
aligned among themselves.  If you want a different alignment, you
can specify it with the key \f(CW\*(C`align_title_lines\*(C'\fR.  Again, only \f(CW\*(C`left\*(C'\fR,
\&\f(CW\*(C`right\*(C'\fR or \f(CW\*(C`center\*(C'\fR are allowed.
.Sp
Do not put other keys than those mentioned above (\fItitle\fR, \fIalign\fR,
\&\fIalign_title\fR, \fIalign_title_lines\fR, and \fIsample\fR) into a hash that
specifies a column.  Most would be ignored, but some would confuse the
interpreter (in particular, \fIis_sep\fR has to be avoided).
.IP "Separators as strings" 4
.IX Item "Separators as strings"
A separator must be given as a reference to a string (often a literal,
like \f(CW\*(C`\e\*(Aq | \*(Aq\*(C'\fR), any string that is given directly describes a column.
.Sp
It is usually just a (short) string that will be printed between
table columns on all table lines instead of the default single
blank.  If you specify two separators (on two lines), the first one
will be used in the title and the other in the body of the table.
.IP "Separators as Hashes" 4
.IX Item "Separators as Hashes"
The hash representation of a separator has the format
.Sp
.Vb 5
\&    {
\&        is_sep => 1,
\&        title  => $title,
\&        body   => $body,
\&    }
.Ve
.Sp
\&\f(CW$title\fR is the separator to be used in the title area and \f(CW$body\fR
the one for the body.  If only one is given, the other is used for
both.  If none is given, a blank is used.  If one is shorter than
the other, it is blank filled on the right.
.Sp
The value of \f(CW\*(C`is_sep\*(C'\fR must be set to a true value, this is the
distinguishing feature of a separator.
.SS "Alignment"
.IX Subsection "Alignment"
The original documentation to Text::Aligner contains all the details
on alignment specification, but here is the rundown:
.PP
The possible alignment specifications are \fIleft\fR, \fIright\fR, \fIcenter\fR,
\&\fInum\fR and \fIpoint\fR (which are synonyms), and \fIauto\fR.  The first
three explain themselves.
.PP
\&\fInum\fR (and \fIpoint\fR) align the decimal point in the data, which is
assumed to the right if none is present.  Strings that aren't
numbers are treated the same way, that is, they appear aligned
with the integers unless they contain a \*(L".\*(R".  Instead of the
decimal point \*(L".\*(R", you can also specify any other string in
the form \fInum(,)\fR, for instance.  The string in parentheses
is aligned in the data.  The synonym \fIpoint\fR for \fInum\fR may be
more appropriate in contexts that deal with arbitrary
strings, as in \fIpoint(=>)\fR (which might be used to align certain
bits of Perl code).
.PP
\&\fIregex alignment\fR is a more sophisticated form of point alignment.
If you specify a regular expression, as delivered by \f(CW\*(C`qr//\*(C'\fR, the start
of the match is used as the alignment point.  If the regex contains
capturing parentheses, the last submatch counts.  [The usefulness of
this feature is under consideration.]
.PP
\&\fIauto\fR alignment combines numeric alignment with left alignment.
Data items that look like numbers, and those that don't, form two
virtual columns and are aligned accordingly: \f(CW\*(C`num\*(C'\fR for numbers and
\&\f(CW\*(C`left\*(C'\fR for other strings.  These columns are left-aligned with
each other (i.e. the narrower one is blank-filled) to form the 
final alignment.
.PP
This way, a column that happens to have only numbers in the data gets
\&\fInum\fR alignment, a column with no numbers appears \fIleft\fR\-aligned,
and mixed data is presented in a reasonable way.
.SS "Column Selection"
.IX Subsection "Column Selection"
Besides creating tables from scratch, they can be created by
selecting columns from an existing table.  Tables created this
way contain the data from the columns they were built from.
.PP
This is done by specifying the columns to select by their index
(where negative indices count backward from the last column).
The same column can be selected more than once and the sequence
of columns can be arbitrarily changed.  Separators don't travel
with columns, but can be specified between the columns at selection
time.
.PP
You can make the selection of one or more columns dependent on
the data content of one of them.  If you specify some of the columns
in angle brackets [...], the whole group is only included in the
selection if the first column in the group contains any data that
evaluates to boolean true.  That way you can de-select parts of a
table if it contains no interesting data.  Any column separators
given in brackets are selected or deselected along with the rest
of it.
.SH "PUBLIC METHODS"
.IX Header "PUBLIC METHODS"
.SS "Table Creation"
.IX Subsection "Table Creation"
.IP "\fInew()\fR" 4
.IX Item "new()"
.Vb 1
\&    my $tb = Text::Table\->new( $column, ... );
.Ve
.Sp
creates a table with the columns specified.  A column can be proper column
which contains and displays data, or a separator which tells how to fill
the space between columns.  The format of the parameters is described under
\&\*(L"Column Specification\*(R". Specifying an invalid alignment for a column
results in a warning if these are allowed.
.Sp
If no columns are specified, the number of columns is taken from the first
line of data added to the table.  The effect is as if you had specified
\&\f(CW\*(C`Text::Table\->new( ( \*(Aq\*(Aq) x $n)\*(C'\fR, where \f(CW$n\fR is the number of
columns.
.IP "\fIselect()\fR" 4
.IX Item "select()"
.Vb 1
\&    my $sub = $tb\->select( $column, ...);
.Ve
.Sp
creates a table from the listed columns of the table \f(CW$tb\fR, including
the data.  Columns are specified as integer indices which refer to
the data columns of \f(CW$tb\fR.  Columns can be repeated and specified in any
order.  Negative indices count from the last column.  If an invalid
index is specified, a warning is issued, if allowed.
.Sp
As with \*(L"\fInew()\fR\*(R", separators can be interspersed among the column
indices and will be used between the columns of the new table.
.Sp
If you enclose some of the arguments (column indices or separators) in
angle brackets \f(CW\*(C`[...]\*(C'\fR (technically, you specify them inside an
arrayref), they form a group for conditional selection.  The group is
only included in the resulting table if the first actual column inside
the group contains any data that evaluate to a boolean true.  This way
you can exclude groups of columns that wouldn't contribute anything
interesting.  Note that separators are selected and de-selected with
their group.  That way, more than one separator can appear between
adjacent columns.  They don't add up, but only the rightmost separator
is used.  A group that contains only separators is never selected.
[Another feature whose usefulness is under consideration.]
.SS "Status Information"
.IX Subsection "Status Information"
.IP "\fIn_cols()\fR" 4
.IX Item "n_cols()"
.Vb 1
\&    $tb\->n_cols
.Ve
.Sp
returns the number of columns in the table.
.IP "\fIwidth()\fR" 4
.IX Item "width()"
.Vb 1
\&    $tb\->width
.Ve
.Sp
returns the width (in characters) of the table.  All table lines have
this length (not counting a final \*(L"\en\*(R" in the line), as well as the
separator lines returned by \f(CW$tb\fR\->\fIrule()\fR and \f(CW$b\fR\->\fIbody_rule()\fR.
The width of a table can potentially be influenced by any data item
in it.
.IP "\fIheight()\fR" 4
.IX Item "height()"
.Vb 1
\&    $tb\->height
.Ve
.Sp
returns the total number of lines in a table, including title lines
and body lines. For orthogonality, the synonym \fItable_height()\fR also
exists.
.IP "\fItable_height()\fR" 4
.IX Item "table_height()"
Same as \f(CW\*(C`$table\->height()\*(C'\fR.
.IP "\fItitle_height()\fR" 4
.IX Item "title_height()"
.Vb 1
\&    $tb\->title_height
.Ve
.Sp
returns the number of title lines in a table.
.IP "\fIbody_height()\fR" 4
.IX Item "body_height()"
.Vb 1
\&    $tb\->body_height
.Ve
.Sp
returns the number of lines in the table body.
.IP "\fIcolrange()\fR" 4
.IX Item "colrange()"
.Vb 1
\&    $tb\->colrange( $i)
.Ve
.Sp
returns the start position and width of the \f(CW$i\fR\-th column (counting from 0)
of the table.  If \f(CW$i\fR is negative, counts from the end of the table.  If \f(CW$i\fR
is larger than the greatest column index, an imaginary column of width 0
is assumed right of the table.
.SS "Data Loading"
.IX Subsection "Data Loading"
.IP "\fIadd()\fR" 4
.IX Item "add()"
.Vb 1
\&    $tb\->add( $col1, ..., $colN)
.Ve
.Sp
adds a data line to the table, returns the table.
.Sp
\&\f(CW$col1\fR, ..., \f(CW$colN\fR are scalars that
correspond to the table columns.  Undefined entries are converted to '',
and extra data beyond the number of table columns is ignored.
.Sp
Data entries can be multi-line strings.  The partial strings all go into
the same column.  The corresponding fields of other columns remain empty
unless there is another multi-line entry in that column that fills the
fieds.  Adding a line with multi-line entries is equivalent to adding
multiple lines.
.Sp
Every call to \f(CW\*(C`add()\*(C'\fR increases the body height of the table by the
number of effective lines, one in the absence of multiline entries.
.IP "\fIload()\fR" 4
.IX Item "load()"
.Vb 1
\&    $tb\->load( $line, ...)
.Ve
.Sp
loads the data lines given into the table, returns the table.
.Sp
Every argument to \f(CW\*(C`load()\*(C'\fR represents a data line to be added to the
table.  The line can be given as an array(ref) containing the data
items, or as a string, which is split on whitespace to retrieve the
data.  If an undefined argument is given, it is treated as an
empty line.
.IP "\fIclear()\fR" 4
.IX Item "clear()"
.Vb 1
\&    $tb\->clear;
.Ve
.Sp
deletes all data from the table and resets it to the state after
creation.  Returns the table.  The body height of a table is 0 after
\&\f(CW\*(C`clear()\*(C'\fR.
.SS "Table Output"
.IX Subsection "Table Output"
The three methods \f(CW\*(C`table()\*(C'\fR, \f(CW\*(C`title()\*(C'\fR, and \f(CW\*(C`body()\*(C'\fR are very similar.
They access different parts of the printable output lines of a table with
similar methods.  The details are described with the \f(CW\*(C`table()\*(C'\fR method.
.IP "\fItable()\fR" 4
.IX Item "table()"
The \f(CW\*(C`table()\*(C'\fR method returns lines from the entire table, starting
with the first title line and ending with the last body line.
.Sp
In array context, the lines are returned separately, in scalar context
they are joined together in a single string.
.Sp
.Vb 3
\&    my @lines = $tb\->table;
\&    my $line  = $tb\->table( $line_number);
\&    my @lines = $tb\->table( $line_number, $n);
.Ve
.Sp
The first call returns all the lines in the table.  The second call
returns one line given by \f(CW$line_number\fR.  The third call returns \f(CW$n\fR
lines, starting with \f(CW$line_number\fR.  If \f(CW$line_number\fR is negative, it
counts from the end of the array.  Unlike the \f(CW\*(C`select()\*(C'\fR method,
\&\f(CW\*(C`table()\*(C'\fR (and its sister methods \f(CW\*(C`title()\*(C'\fR and \f(CW\*(C`body()\*(C'\fR) is
protected against large negative line numbers, it truncates the
range described by \f(CW$line_number\fR and \f(CW$n\fR to the existing lines.  If
\&\f(CW$n\fR is 0 or negative, no lines are returned (an empty string in scalar
context).
.IP "\fIstringify()\fR" 4
.IX Item "stringify()"
Returns a string representation of the table. This method is called for
stringification by overload.
.Sp
.Vb 1
\&    my @table_strings = map { $_\->stringify() } @tables;
.Ve
.IP "\fItitle()\fR" 4
.IX Item "title()"
Returns lines from the title area of a table, where the column titles
are rendered.  Parameters and response to context are as with \f(CW\*(C`table()\*(C'\fR,
but no lines are returned from outside the title area.
.IP "\fIbody()\fR" 4
.IX Item "body()"
Returns lines from the body area of a table, that is the part where
the data content is rendered, so that \f(CW$tb\fR\->body( 0) is the first data
line.  Parameters and response to context are as with \f(CW\*(C`table()\*(C'\fR.
.IP "\fIrule()\fR" 4
.IX Item "rule()"
.Vb 6
\&    $tb\->rule;
\&    $tb\->rule( $char);
\&    $tb\->rule( $char, $char1);
\&    $tb\->rule( sub { my ($index, $len) = @_; }, 
\&               sub { my ($index, $len) = @_; },
\&    );
.Ve
.Sp
Returns a rule for the table.
.Sp
A rule is a line of table width that can be used between table lines
to provide visual horizontal divisions, much like column separators
provide vertical visual divisions.  In its basic form (returned by the
first call) it looks like a table line with no data, hence a blank
line except for the non-blank parts of any column-separators.  If
one character is specified (the second call), it replaces the blanks
in the first form, but non-blank column separators are retained.  If
a second character is specified, it replaces the non-blank parts of
the separators.  So specifying the same character twice gives a solid
line of table width.  Another useful combo is \f(CW\*(C`$tb\-<rule( \*(Aq\-\*(Aq, \*(Aq+\*(Aq)\*(C'\fR,
together with separators that contain a single nonblank \*(L"|\*(R", for a
popular representation of line crossings.
.Sp
\&\f(CW\*(C`rule()\*(C'\fR uses the column separators for the title section if there
is a difference.
.Sp
If callbacks are specified instead of the characters, then they receive the
index of the section of the rule they need to render and its desired length in
characters, and should return the string to put there. The indexes given
are 0 based (where 0 is either the left column separator or the leftmost
cell) and the strings will be trimmed or extended in the replacement.
.IP "\fIbody_rule()\fR" 4
.IX Item "body_rule()"
\&\f(CW\*(C`body_rule()\*(C'\fR works like <\fIrule()\fR>, except the rule is generated using
the column separators for the table body.
.SS "Warning Control"
.IX Subsection "Warning Control"
.IP "\fIwarnings()\fR" 4
.IX Item "warnings()"
.Vb 4
\&    Text::Table\->warnings();
\&    Text::Table\->warnings( \*(Aqon\*(Aq);
\&    Text::Table\->warnings( \*(Aqoff\*(Aq):
\&    Text::Table\->warnings( \*(Aqfatal\*(Aq):
.Ve
.Sp
The \f(CW\*(C`warnings()\*(C'\fR method is used to control the appearance of warning
messages while tables are manipulated.  When Text::Table starts, warnings
are disabled.  The default action of \f(CW\*(C`warnings()\*(C'\fR is to turn warnings
on.  The other possible arguments are self-explanatory.  \f(CW\*(C`warnings()\*(C'\fR
can also be called as an object method (\f(CW\*(C`$tb\->warnings( ...)\*(C'\fR).
.SH "VERSION"
.IX Header "VERSION"
This document pertains to Text::Table version 1.124
.SH "BUGS"
.IX Header "BUGS"
.IP "o" 4
.IX Item "o"
\&\fIauto\fR alignment doesn't support alternative characters for the decimal
point.  This is actually a bug in the underlying Text::Aligner by the
same author.
.SH "AUTHOR"
.IX Header "AUTHOR"
.SS "\s-1MAINTAINER\s0"
.IX Subsection "MAINTAINER"
Shlomi Fish, <http://www.shlomifish.org/> \- \s-1CPAN ID: \*(L"SHLOMIF\*(R".\s0
.SS "\s-1ORIGINAL AUTHOR\s0"
.IX Subsection "ORIGINAL AUTHOR"
.Vb 4
\&    Anno Siegel
\&    CPAN ID: ANNO 
\&    siegel@zrz.tu\-berlin.de
\&    http://www.tu\-berlin.de/~siegel
.Ve
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
Copyright (c) 2002 Anno Siegel. All rights reserved.
This program is free software; you can redistribute
it and/or modify it under the terms of the \s-1ISC\s0 license.
.PP
(This program had been licensed under the same terms as Perl itself up to
version 1.118 released on 2011, and was relicensed by permission of its
originator).
.PP
The full text of the license can be found in the
\&\s-1LICENSE\s0 file included with this module.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
Text::Aligner, \fIperl\fR\|(1) .

${this.title}

Code Editor : Text::Table.3pm