Hi everyone, I'm working on planning my Python course for this fall, and I'd like to get the group's advise on when I should introduce OOP. I work with Zope a lot and the OO paradigm is pretty deeply embedded there. I've really gotten to like it. (Not that I've mastered it. :-) Now I'm fully aware that Python is just as capable a procedural programming language as it is an OO one. I don't want to skip talking about that side of things, but OOP seems so prevalent in many areas that I'd like to get my students working with it as soon as possible. I'd appreciate any thoughts you might have on this topic. -Tim -- Tim Wilson | Visit Sibley online: | Check out: Henry Sibley HS | http://www.isd197.org | http://www.zope.com W. St. Paul, MN | | http://slashdot.org wilson@visi.com | <dtml-var pithy_quote> | http://linux.com
I agree: no need to delay OOP. Just as many urban areas are going directly to cell phone, because the land lines system is a mess (e.g. Budapest), so might newbies to programming start directly with OOP. No need for this "ontogeny recapitulates phylogeny" nonsense -- not really true in bio either, despite the hype. And it's not all that "either/or" either: procedural code is embedded inside of objects. Write a standard procedure and then swallow it, make it a part of some "thing" -- as easy to understand as digestion. The objects model is everywhere: any electronic gizo exports its API via its control panel. Interfaces to behind-the-scenes guts -- what could be more everyday? Kirby
participants (2)
-
Kirby Urner -
Timothy Wilson