Ed Leafe wrote:
> On May 2, 2007, at 12:12 PM, [EMAIL PROTECTED] wrote:
>
>> For the solutions I've came up with, I would like specifically to
>> hear comments about:
>
> I've been meaning to get to this all day, but I've been swamped. I
> just wanted to let you know that I'll take a look at this as soon as
> I can.
Me too. For now, let me just offer a comment on the VirtualFields. The
way you have it:
self.VirtualFields = {...}
would overwrite any previously-defined VirtualFields. Now, you are
saying "there aren't any previously-defined VirtualFields" which is
true, however what if in the future you were to subclass this class, and
the subclass were to call self.super() after setting its own
VirtualFields? The super's VirtualFields would overwrite it. Better
(IMO) to do:
self.VirtualFields["field_name"] = func
and then any previously-defined ones wouldn't get overwritten. This
principle applies to all properties that are mutable, such as dicts and
lists.
--
pkm ~ http://paulmcnett.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/%(messageid)s
