Storing the length of all the overloading names saves a strlen() in a
[p5sagit/p5-mst-13.2.git] / t / pod / headings.t
CommitLineData
360aca43 1BEGIN {
9c6ed6d7 2 use File::Basename;
3 my $THISDIR = dirname $0;
4 unshift @INC, $THISDIR;
360aca43 5 require "testp2pt.pl";
6 import TestPodIncPlainText;
7}
8
9my %options = map { $_ => 1 } @ARGV; ## convert cmdline to options-hash
10my $passed = testpodplaintext \%options, $0;
11exit( ($passed == 1) ? 0 : -1 ) unless $ENV{HARNESS_ACTIVE};
12
13
14__END__
15
16
17#################################################################
18 use Pod::Usage;
19 pod2usage( VERBOSE => 2, EXIT => 1 );
20
21=pod
22
23=head1 NAME
24
25B<rdb2pg> - insert an rdb table into a PostgreSQL database
26
27=head1 SYNOPSIS
28
29B<rdb2pg> [I<param>=I<value> ...]
30
31=head1 PARAMETERS
32
33B<rdb2pg> uses an IRAF-compatible parameter interface.
34A template parameter file is in F</proj/axaf/simul/lib/uparm/rdb2pg.par>.
35
36=over 4
37
38=item B<input> I<file>
39
40The B<RDB> file to insert into the database. If the given name
41is the string C<stdin>, it reads from the UNIX standard input stream.
42
43
44=back
45
46=head1 DESCRIPTION
47
48B<rdb2pg> will enter the data from an B<RDB> database into a
49PostgreSQL database table, optionally creating the database and the
50table if they do not exist. It automatically determines the
51PostgreSQL data type from the column definition in the B<RDB> file,
52but may be overriden via a series of definition files or directly
53via one of its parameters.
54
55The target database and table are specified by the C<db> and C<table>
56parameters. If they do not exist, and the C<createdb> parameter is
57set, they will be created. Table field definitions are determined
58in the following order:
59
60=cut
61
62#################################################################
63
64results in:
65
66
67#################################################################
68
69 rdb2pg - insert an rdb table into a PostgreSQL database
70
71 rdb2pg [*param*=*value* ...]
72
73 rdb2pg uses an IRAF-compatible parameter interface. A template
74 parameter file is in /proj/axaf/simul/lib/uparm/rdb2pg.par.
75
76 The RDB file to insert into the database. If the given name is
77 the string `stdin', it reads from the UNIX standard input
78 stream.
79
80 rdb2pg will enter the data from an RDB database into a
81 PostgreSQL database table, optionally creating the database and
82 the table if they do not exist. It automatically determines the
83 PostgreSQL data type from the column definition in the RDB file,
84 but may be overriden via a series of definition files or
85 directly via one of its parameters.
86
87 The target database and table are specified by the `db' and
88 `table' parameters. If they do not exist, and the `createdb'
89 parameter is set, they will be created. Table field definitions
90 are determined in the following order:
91
92
93#################################################################
94
95while the original version of Text (using pod2text) gives
96
97#################################################################
98
99NAME
100 rdb2pg - insert an rdb table into a PostgreSQL database
101
102SYNOPSIS
103 rdb2pg [*param*=*value* ...]
104
105PARAMETERS
106 rdb2pg uses an IRAF-compatible parameter interface. A template
107 parameter file is in /proj/axaf/simul/lib/uparm/rdb2pg.par.
108
109 input *file*
110 The RDB file to insert into the database. If the given name
111 is the string `stdin', it reads from the UNIX standard input
112 stream.
113
114DESCRIPTION
115 rdb2pg will enter the data from an RDB database into a
116 PostgreSQL database table, optionally creating the database and
117 the table if they do not exist. It automatically determines the
118 PostgreSQL data type from the column definition in the RDB file,
119 but may be overriden via a series of definition files or
120 directly via one of its parameters.
121
122 The target database and table are specified by the `db' and
123 `table' parameters. If they do not exist, and the `createdb'
124 parameter is set, they will be created. Table field definitions
125 are determined in the following order:
126
127
128#################################################################
129
130
131Thanks for any help. If, as your email indicates, you've not much
132time to look at this, I can work around things by calling pod2text()
133directly using the official Text.pm.
134
135Diab
136
137-------------
138Diab Jerius
139djerius@cfa.harvard.edu
140