Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I was having a hard time understanding how to use POD documentation when I was habitually using block comments for all my documentation purposes. After reading the Perl Programming Documentation about POD, I found that, where I usually used comment blocks to describe functions, POD is just as effective if not more so. I then wondered, what is the purpose of commenting when POD exists (besides TMTOWTDI). I then realized that I should document my functions using POD and make small notes about the actual code using comments.

For example:

=pod =head2 mySubroutine Takes no argument. This is a sample example to show my idea about documentation using both comments and POD. =cut sub mySubroutine { print 'This is a sample subroutine.', "\n"; # prints this text because it's a simple example. } mySubroutine();

I hope this helps anyone who is just discovered POD and is either now confused about the purpose of both comments and POD or is looking for another method of documenting their code. If anyone has any comments (ha, comments), suggestions, or corrections for this node, please let me know!

This is what works for me, and, as always, TMTOWTDI.

"It's funny, the claw isn't what you should be worried about" -The Raven

In reply to Documentation: POD vs Comments by ravenclaw

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others surveying the Monastery: (8)
    As of 2018-06-25 17:59 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (128 votes). Check out past polls.