Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Re^5: RFR: Inside-out classes - a Class::InsideOut primer

by Joost (Canon)
on Mar 16, 2007 at 15:38 UTC ( #605175=note: print w/replies, xml ) Need Help??

in reply to Re^4: RFR: Inside-out classes - a Class::InsideOut primer
in thread RFR: Inside-out classes - a Class::InsideOut primer

I agree. What I meant to say is that every property that's relevant to the classes' user should have some way of getting and maybe setting it. Basically, I regard all properties as implementation details and private and they should only be exposed (via accessors) if that's useful. I certainly didn't mean that all properties should have a direct public interface. A classes' user doesn't have to know or care if a method is just a plain accessor or something else. All that matters is that the public API allows the user to do everything relevant and hide everything that's not.

  • Comment on Re^5: RFR: Inside-out classes - a Class::InsideOut primer

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://605175]
[erix]: and good morning (sorry :))
[Corion]: erix: Naah, I just saw the announcement and remembered that discussion. Maybe I'll try building a DBD::SQLite with the zip stuff built-in, just for fun
[Corion]: Oh - and a good morning to you too :)
[erix]: we have these largish series (dozens) of largisch (1-2 GB) tabsep files that might be shrunk a bit in this way. Bound to get a bit slower but that doesn't matter too much for us

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (6)
As of 2018-01-24 08:57 GMT
Find Nodes?
    Voting Booth?
    How did you see in the new year?

    Results (256 votes). Check out past polls.