|
|
Richard Heathfield <rjh@xxxxxxxxxxxxxxx> writes:
>Chris McDonald said:
>> Perhaps it's your wording, but for "beginning C programmers" I would
>> seriously recommend using only a single C compiler, and one that
>> co-exists well with their preferred operating system (or the one used
>> for instruction).
>>
>> Using "as many C compilers as possible", presumably each with different
>> incantations and interpretations of standards, would only confuse the
>> learning of the language itself.
>I don't think it would, if it were done properly.
>
>....
>
>I rather regret not being introduced to multiple compilers during that
>time. It would have significantly hastened my nascent understanding of the
>idea of a "standard language".
Sorry, but my 25 years (and counting) of teaching languages to 4000+
novice programmers provides me with a different impression of what is
possible. And it's not a matter of doing it "properly", it's a matter
of what is possible given the constraints of the teaching environment.
Today we have 3 primary operating systems (used in the teaching
of undergrads) and a number of possible C compilers (on each OS).
Trying to actually teach a new programming language, in 12 weeks, amidst
the variety of platforms, attendance patterns, declining enrolments,
and declining motivations, can only hope to see success in an environment
where technical distractions are minimized.
Lecturing that "a C compiler's output file may be named with the -o
option, unless you're using the XYZ compiler, where it's the -q option...."
is about as motivating to waivering CS students as "all sulphates are soluble,
except for gold sulphate and ..." was to me as a waivering Chemistry student.
______________________________________________________________________________
Dr Chris McDonald E: chris@xxxxxxxxxxxxxxx
Computer Science & Software Engineering W: http://www.csse.uwa.edu.au/~chris
The University of Western Australia, M002 T: +618 6488 2533
Crawley, Western Australia, 6009 F: +618 6488 1089
|
|