Thanks for the clarifications, good to know both options (receiver and receiverless) are both in the mix.
Our use of 'procedural' may confuse some students as OO syntax is eminently step-by-step with flow of control and all the rest of it, very recognizably procedural the way I learned the term, with or without the explicit dot notation (which is difficult to hide in real Python). I'm inclined to *not* see 'procedural' and 'object oriented' as orthogonal concepts i.e. they mix together. Where I do see a big dichotomy is in whether one is expected to define new classes oneself, or simply use the ones provided. Apparently early versions of Visual Basic were "read only" in terms of not having a class defining infrastructure, merely giving developers access to canned OCX objects (instances) with canned APIs, but I could be wrong, that's not a track I've ever followed, even to this very day. As I mention in my Chicago talk, I tell my students "I've never heard of procedural programming, it gives me the creeps" but that's just a rhetorical device to get the ball rolling, as I start with dot notation immediately, within the first 10 minutes. But that's because I'm teaching core Python, not another language *implemented* in core Python. These aren't little children. They may have done Logo or other 3rd person avatar controlling (ala Sims) well before taking my class, so I presume this as background, allude to Sims as "objects" and so on, project a YouTube or two if they seem unclear what I'm talking about. Kirby _______________________________________________ Edu-sig mailing list [email protected] http://mail.python.org/mailman/listinfo/edu-sig
