OK, I'll take a chance because as you say I don't know the
details of what you are building. And if its a Framework
for persistence, or an IDE for building persistence then
get/set may be your best bet - after all that's why Java
Beans have them so that Java IDEs can manipulate object
properties at
I appreciate your input. You are correct. I read a bunch of LoD stuff
Northeastern website. It codified a bunch of things that I had been
working through.
But what you are not seeing (I must be terrible at this, always hard
to tell how much code to post) is this chunk of code represents an
idea ab
David Driver wrote:
> So I have been trying to figure out how to get around doing getters
> and setters and still have an oo way to inherit and apply business
> rules. This is what I have some up with so far. Is there any better
> way?
Hmm. I'm not sure what this has to do with getters and setters
> So I have been trying to figure out how to get around doing getters
> and setters and still have an oo way to inherit and apply business
> rules.
I think you are missing the point a wee bit.
The object should not allow you to access its internal data.
You should not *need* to access its inter
So I have been trying to figure out how to get around doing getters
and setters and still have an oo way to inherit and apply business
rules. This is what I have some up with so far. Is there any better
way?
class RuleViolationError(Exception):
def __init__(self, msg):
self.msg = msg
