Re: [Modeling-users] ModelMasons refactored

[Mario R. <ma...@ru...>]

On mardi, avr 22, 2003, at 15:15 Europe/Amsterdam, Mario Ruggier wrote:
> On mardi, avr 22, 2003, at 14:07 Europe/Amsterdam, Sebastien Bigaret 
> wrote:
>> Mario Ruggier <ma...@ru...> writes:

[snip]

>>>> BTW: Mario proposed that the generated class initializer could be:
>>>>>   def __init__(self,att1=None,att2=None):
>>>> instead of
>>>>>   def __init__(self):
>>>>
>>>>   Are we ok we go for it?

A propos de previous post on KeyValueCoding names -- this proposition
lacks a minor thing, and that is inside the __init__ body, the 
attribute values
should be set using KeyValueCoding, not to bypass any custom code
in the get/set methods for each attribute.

Additional proposal ;)
How about adding __slots__ to all custom objects?
It seems to me that this is exactly the kind of usage that this was
intended for, and will reduce memory usage for cases of *many*
instances of custom objects. Works only for 2.2, but if present should
not affect 2.1 instances in any way.

mario