L<name> A link (cross reference) to name
L<name> manual page
L<name/ident> item in manual page
L<name/"sec"> section in other manual page
L<"sec"> section in this manual page
(the quotes are optional)
same as above but only 'text' is used for output.
(Text can not contain the characters '/' and '|',
and should contain matched '<' or '>')
will be up updated to make support for L<link text|url>
so to be on the safe side (with ye old modules), just use L<url> or don't use L at all cause pod2html will autolink it.
Now, what pod2html will do is try to autolink C<=item functioname>
if you use C<$foo-E<gt>method>.
Pod::Html will also try to autolink to any core perl functions and the like.
This has nothing to do with pod, it's just extra fluff (i like it).
What everybody wants to do is use podchecker. You wanna lookout for "multiple link targets" warnings, like if you have =headN FOO twice.
MJD says you
can't just make shit up and expect the computer to know what you mean, retardo!
I run a Win32 PPM
repository for perl 5.6x+5.8x. I take requests.
** The Third rule of perl club is a statement of fact: pod is sexy.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.