comment on

Thank you

Yes, I did wonder if I was going to start a major debate about POD being inline or clumped at the bottom. I took the view, without thinking about it too much, that it is probably easier to write it next to the subroutines it relates to whilst developing the module. Then, once that subroutine is proven working and shouldn't need touching again, shift its POD to the bottom out of the way. Whether this moving would ever happen of course is up for debate!

For this one I don't need to worry about CPAN rendering but I still want to try and get it right for the future.

Is it worth also trying to write tests for this - again for practice and learning - if so, where would I start?

In reply to Re^2: [RFC] Review of module code and POD by Bod
in thread [RFC] Review of module code and POD by Bod

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> <u> <ul>
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 intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks