in reply to Re: Documenting non-public OO components
in thread Documenting non-public OO components
I may end up doing something akin to that. Since Plucene is a large library, I can put the explanation in one central place (probably the main module), then hew to the convention elsewhere. That's way better than what I was considering before; it's nice to see your example.
|
---|
In Section
Meditations