Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re^2: Documenting non-public OO components

by creamygoodness (Curate)
on Sep 06, 2005 at 16:21 UTC ( #489590=note: print w/replies, xml ) Need Help??

in reply to Re: Documenting non-public OO components
in thread Documenting non-public OO components

Well, the big project I'm working on is an overhaul of Plucene, the perl port of the Java Lucene search engine library I'm moving a couple things around, but for the most part it should stay as is, and Lucene's pretty well designed.

Beyond that, I'm not sure that it makes sense to constrain development via a severe public-class-all-things-public / devel-class-all-things-devel split. You could do that, but there are bound to be occasions when you wish you could add a protected method to that public class. For sure, it's a good idea to divide responsibility, but unless you take draconian measures, the problem still exists.

Marvin Humphrey
Rectangular Research ―
  • Comment on Re^2: Documenting non-public OO components

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://489590]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (7)
As of 2022-12-05 12:17 GMT
Find Nodes?
    Voting Booth?

    No recent polls found