[Bese-devel] [PATCH] wrapping-standard method combination
Vladimir Sekissov
svg at surnet.ru
Sat Nov 26 00:10:10 UTC 2005
mb> > With this order superclass wrapping methods can't need to care about
mb> > possible subclass implementations and subclass methods don't be
mb> > confused by superclass wrapping method's demonic changes of arguments
mb> > and instance state.
mb>
mb> can you describe this problem more? i've not run into it and i'm
mb> curious what the issue is.
As for me I want to properly initialize optional and keyword arguments
of methods and wrapping ones are the only right place for doing this
(in the order from superclass to subclasses).
Other things I can do with other methods but wrapping methods seems
for me the only right place for initialization.
Best Regards,
Vladimir Sekissov
More information about the bese-devel
mailing list