> necessarily undo encapsulation, as they may perform
> range/contract/integrity checking.
encapsulation doesn't imply any kind of validation does it? [but
certainly a side effect of dump truck loads of getters and setters]
but yea i was really just getting at the point that obsession of a
principle can ultimately undermine it. i mentioned this to my
coworker and his response was 'just use eclipse to generate them' i.e.
its just mindless dogma at this point.
> private:
> int foo;
> public:
> int GetFoo() { return this->foo; }
> void SetFoo(int foo) { this->foo = foo; }
>
> // which leads to things like
> instance.GetFoo() = 10; // super icky
c++ !
> ... then you're probably not on this mailing list. I hope anyway. :)
yea java bashing is pretty safe in these parts :)
_______________________________________________
Sdruby mailing list
[email protected]
http://lists.sdruby.com/mailman/listinfo/sdruby
