Mon, 3 Dec 2001 23:28:26 +0100
Thanks for this argument. I did some considerations
on this topic for myself.
My experience is, that my students understand well this
overloading of /, but they tend to forget it when writing
some useful programs doing some maths. Especially when
using the input-statement one often arrives at integers
unintentionally. So should we type-cast every input with
float or resort only to use raw_input?
On the other hand the main point here is the difference between
two kinds of division, which of course must be taught - and perhaps
can be taught more easily - also in the python -Qnew interpreter.
If those two are accomplished by two different operators or
by a single overloaded one is - IMHO ;-) - secondary to that.
Thanks another time for the discussion
----- Original Message -----
To: <email@example.com>; <firstname.lastname@example.org>; <email@example.com>
Sent: Monday, December 03, 2001 2:23 PM
Subject: RE: [Tutor] Division
> > > As I'm starting to give a new course 'Introduction to
> > > programming' in Jan 2002. It's for young students in the
> > > age of 15/16. (Of course) I shall use Python.
> > > I'd consider it an advantage not to confuse my students
> > > in the beginning with the specialities the overlaoding of
> > > the division-operator (although I had to do so for several times
> > > until now). But neither with the import from future
> > > statement.
> Just one point is that maybe for an education in programming
> they should use the old style division behaviour - its how
> the vast majority of programming languages work and is a
> great way to seehow the computer is working under the covers.
> If you want to use programming as part of another topic then
> use new division but if you want to teach programming
> principles stick to old style - its much more univesally
> applicable and infornative IMHO.
> Alan G