Re: aggregate() und overload()

Kristian wrote: > If overload() allows for __get_x(), though, this is bad design. > The reason for this is that we get namespace pollution and, > again (*), automatically called callback functions with a > variable name. There will interoperate badly with inheritance, > with dynamically created, undeclared instance variables and with > aggregate(). > > Recommendation: > > If overload() indeed supports variably named callback functions > such as __get_x(), support for this should be removed in order > to avoid a number of possible inconsistencies and namespace > pollution. Please expound on this. I would like to hear specific problems you see existing with __get_x() callbacks. -Andrei "Everything should be made as simple as possible, but not simpler." -- Albert Einstein