Re: Which constructor?
Stuart <DerTopper@web.de> writes:
IMHO, it makes little sense to teach object-orientation to people who
never had written code before. The best you can expect is probably that
they can write some crappy exercise code, but it takes many years to get
to grips with object orientation (or better: how to divide the problem
space into components).
Yes, I agree. The people who go into the OOP-course, however, have
decided that they want to learn this now for whatever reason. They
do not necessarily have to be the same people as those who were in
the preceding beginner's course. Everyone is free to take the
beginners course, wait 10 years, and then take the ?advanced? course.
I have translated a famous English text on this subject into German:
http://purl.net/stefan_ram/html/21-tage
.
to translate this), and as soon as objects got introduced, almost
everybody was lost (except for those who were already able to write
programs before they attended this course).
I am giving exercises in class and observe how the students cope
with those exercises. From this, I know that not everybody is lost
in my class. OTOH, not everybody can solve every exercise.
enough. Most courses use some convoluted problems a la "animal->eat()"
I try to avoid this as I am giving classes for adults and the
?cow makes moo? might seem too childish for them. A better example
for inheritance might be a range-checking adaptation of ::std::vector.