in reply to Re: Style and Coding Criticism (part 2)
in thread Style and Coding Criticism (part 2)

Or if you're disabling a section of code and want to use POD, use the proper POD tags to disable compilation. =item isn't always seen as a proper beginning of a POD chunk.
While I agree with part 1, part 2 is untrue -- stick to properly formed pod, like
#hey some code followed by a blank line =butter is the pod, and the pod is the butter =cut followed by a blank line, no more pod #and here we have some other code
Even if use fictional pod tags, perl will parse it correctly. You should stay away from hidden pod/code, as the behaviour is not guaranteed in future versions (see Pod::Stripper, perlpod if you don't know what it is).

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.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: Re: Style and Coding Criticism (part 2)
by halley (Prior) on Aug 06, 2003 at 13:00 UTC
    I agree.

    As with Perl syntax, perl will parse a lot of POD constructs which other tools just don't bother to try to read properly. This has been improving, but there are a lot of different tools, from formatters to text editor modes.

    --
    [ e d @ h a l l e y . c c ]