Classes, OOP, Tkinter general comments and detailed questions...

[Alan Gauld]

Alex Martelli wrote:
> "Alan Gauld" <alan.gauld at bt.com> wrote in message
> > as being like interriupt driven in assembler... an event
> > arrives somewhat like a hardware interrupt and causes an
> Hmmm -- not quite that bad, I would say: interrupts are particularly
> pesky because they are asynchronous, and may arrive at any time,
> _interrupting_ whatever you're doing 

True within the context of a method/event handling function.

> for the next one -- that (in my experience) makes event-driven
> processing nowhere as hard to learn, master _and_ use productively
> as interrupt-driven programming 

Yes, but if you know interrupt programming - as an assembler 
programmer might - then event driven is a piece of cake once you
realize its the same conceptual model :-)

>  you are still thinking about ONE path
> of execution, albeit split up into not-too-big chunks.

Only within an event handler, the flow of control across 
a use-case say is still fragmented and several use-cases 
may be executing simultaneously. Thus all of the context 
saving issues still apply - and for that OO makes it sooooo 
much easier :-)

Alan G