http://qs321.pair.com?node_id=904802


in reply to Re^2: POD troubles
in thread POD troubles

> but the first example that is implied to work on current translators shows =head paragraphs immediately after "plain" paragraph text, which contradicts the bulk of the documentation. Presumably the bulk of the document was not updated with new rules, when this example was tacked on to the end.

could you please post this "wrong" example, I can't find it.

Cheers Rolf

Replies are listed 'Best First'.
Re^4: POD troubles
by John M. Dlugosz (Monsignor) on May 14, 2011 at 11:18 UTC
    OK, it states:

    • Many older Pod translators require the lines before every Pod command and after every Pod command (including "=cut"!) to be a blank line. Having something like this: 
        # - - - - - - - - - - - -
    =item $firecracker->boom()
    This noisily detonates the firecracker object.
    =cut
    sub boom {
    ...
    ...will make such Pod translators completely fail to see the Pod block at all.

    So, "many older translators" don't like that, but current ones do? Otherwise why bother mentioning it?

[reply]
      sigh ... thank you for wasting my time!

      Cheers Rolf

[reply]
        I don't follow. This passage implies that this is supposed to work (except on "some old translators"), but it contradicts the bulk of the document which states that paragraphs must be followed by (actually, terminated with) a blank line.

        I was indeed reading the fine manual, read it end to end several times, and cross-checked versions 10.1 and the current 12.whatever. My observation stands: the example which is implied to work as-is on current translators contradicts the description given earlier. If it's not intended to work, why explain that it must be changed for "older" parsers? If it never works at all, it's a silly thing to say.

        I think I can afford the -- vote. But I think it's unwarranted, after re-reading my post.

[reply]

In Section Seekers of Perl Wisdom