wxPython and macros (was: Why don't people like lisp?

[Tayss]

Brian Kelley <bkelley at wi.mit.edu> wrote:
> This isn't really the case I think, we just have a different idiom for 
> doing something more meaningful.  The solutions in the wxPython world 
> that I have seen do something like this:

This OOP solution looks like the functional one I mentioned earlier,
freezing code in a subclass's function instead of a plain function.
http://groups.google.com/groups?q=g:thl819841888d&dq=&hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&selm=5627c6fa.0310260703.4573b0a%40posting.google.com

But since GUIs often lend themselves well to OOP, I can see this as a
resourceful way to solve this special case.  Making sure that
superclass.__init__() is always called and deciding early to structure
the entire App with OOP.  I'm not a fan of calling overridden methods
from an old init, but life could hurt worse.

-- Tayssir