At 06:33 PM 2001-08-12 +0200, Philip Newton wrote:
>[... quoting perlpodspec ...]
>> Pod content is contained in B<pod blocks>. A pod block starts with a
>> line that matches <m/^=[a-zA-Z]/>, and continues up to the next line
>> that matches C<m/^=cut/> -- or up to the end of the file, if there is
>> no C<m/^=cut/> line.
>[snip]
>Does that mean that the following will be misparsed?
>
> The way to make an indented, bulleted list in POD is to use
> =over with a number, then any number of =item s, followed by
> =back to finish off the list.
No. It only leads to misparses if you have:
The way to stop a POD block and tell perl to start parsing is a
=cut command. Just make sure it's at the start of the line,
and everything'll work right.
And BTW, that's the way perl works currently (if I understand toke.c): a
line matching m/^\w/ means go into pod mode, and subsequent m/^=cut/ line
means go out of pod mode. I'm merely mandating that pod parsers agree with
perl on this. (Actually Perl won't let you drop a "newline =foo
...lines... =cut newline" block just anywhere; it can't be in the middle of
a statement. But it'd be really overly ambitious to make pod parsers try
to wrap their heads around that concept.)
BTW, everything else that you mentioned in the remainder of your message as
being as possible typos or as confusing, was just that, despite my attempts
at proofreading. Quite helpful, and I'll make appropriate changes to the
next draft.
--
Sean M. Burke [EMAIL PROTECTED] http://www.spinn.net/~sburke/
