> Another way people write switch: > > def switch(choice): > if 0<choice<len(functions): ...
This seems a good thing to do. In terms of complexity, functions come after selection, and that is how they are sequenced in the Python First pack. The material is based on functions all way, from the very beginning, but a systematic coverage of functions is offered *after* control structures. Thus, I would not use functions as parameters or list/tuple members as early as when I cover selection. Fortunately, I can possibly add the implementation of switch (above) as an optional lab in the chapter on functions or in the chapter on lists and dictionaries. [Detailed self-guided labs in Python First are fundamental in 'teaching programming as a habit' - I would love to write on this in a later post.] I know this list is a most sophisticated Python audience. Any feedback is appreciated. I can also explain my chosen pedagogy, should that need arise. Cheers, Atanas Atanas Radenski -- Visit http://studypack.com for new Python and Java resources. > -----Original Message----- > From: kirby urner [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 08, 2006 7:51 AM > To: Radenski, Atanas > Cc: [email protected] > Subject: Re: [Edu-sig] Python First: Free access for educators > > Cool, I'm in. Checking out your moodle. > > Another way people write switch: > > def switch(choice): > if 0<choice<len(functions): _______________________________________________ Edu-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/edu-sig
