in reply to Documenting non-public OO components

Read the docs for Pod::Coverage. You can easily specify additional items to consider private and not needing coverage with also_private. If you don't want to take that extra step, just document them as public or private in the pod, either inline -- or better yet -- in sections marked "PUBLIC METHODS", "PRIVATE METHODS" etc.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

Replies are listed 'Best First'.
Re^2: Documenting non-public OO components
by creamygoodness (Curate) on Sep 06, 2005 at 16:36 UTC
    in sections marked "PUBLIC METHODS", "PRIVATE METHODS"

    This, I like. :)

    I will be adopting your suggestion. It solves 90% of the problem, since methods occupy most of the protected/package OO terrain.

    --
    Marvin Humphrey
    Rectangular Research ― http://www.rectangular.com
[reply]

In Section Meditations