Good catch - the name is indeed significant. If I rename the file to have a .pl extension then I see this:
$ mv foo.pod foo.pl
$ perldoc -T foo.pl
No documentation found for "foo.pl".
$ echo $?
1
$
because the contents are now expected to be a perl script and there's nothing in the POD there which refers to "foo.pl". Adding a header with that text for reference satisfies this requirement.
$ cat foo.pl
#!/usr/bin/perl -w
use strict;
=pod
=head1 foo.pl
My documentation.
=cut
$ perldoc -T foo.pl
FOO(1) User Contributed Perl Documentation
+ FOO(1)
foo.pl
My documentation.
perl v5.10.1 2019-03-15
+ FOO(1)
$ echo $?
0
$
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|