Michael Schneider <[EMAIL PROTECTED]> wrote:
>I have been coding in C++ since the late 80's and Java since the late 90's.
>
>I do use private in these languages, with accessors to get at internal
>data.
>
>This has become an ingrained idiom for me.
The question is, has it become a purely instinc
Frederik,
Thank you very much for the info on properties, that is very useful.
Sorry about the public typo, that should have been protected. I should
not post before coffee hits :-)
Happy coding,
Mike
Fredrik Lundh wrote:
> Michael Schneider wrote:
>
>
>>1) mark an object as dirty in a setter
Michael Schneider wrote:
> 1) mark an object as dirty in a setter (anytime the object is changed,
> the dirty flag is set without requiring a user to set the dirty flag
properties.
> 2) enforce value constraints (even if just during debugging)
properties. (when you no longer need to enforce th
On Thursday 29 September 2005 09:08, Michael Schneider wrote:
> Design Intent:
>
> 1) mark an object as dirty in a setter (anytime the object is
> changed, the dirty flag is set without requiring a user to set the
> dirty flag
2 ways: wrap every attribute that is to be set in a property object (in
I have been following this thread with great interest.
I have been coding in C++ since the late 80's and Java since the late 90's.
I do use private in these languages, with accessors to get at internal
data.
This has become an ingrained idiom for me. When I create a python
object, it is natu
