in reply to Documenting non-public OO components
You can place your internal methods in a Foo::Devel package which acts as a helper module and has its own pod. That will seperate both them and their documentation from the public, while leaving them accessible to all.
From the sound of it, your modules seem pretty tightly bound to each other. Could a redesign produce a more natural split of responsibilities?.
After Compline,
Zaxo
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Documenting non-public OO components
by creamygoodness (Curate) on Sep 06, 2005 at 16:21 UTC |
In Section
Meditations