Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!cornell!ho
From: ho@svax.cs.cornell.edu (Alex Ho)
Newsgroups: comp.edu
Subject: Re: Assembler curricula, was Re: using (ugh!  yetch!) assembler
Message-ID: <19851@cornell.UUCP>
Date: 1 Aug 88 15:09:57 GMT
References: <6341@bloom-beacon.MIT.EDU> <60859@sun.uucp> <474@m3.mfci.UUCP> <24134@bu-cs.BU.EDU> <2601@ukecc.engr.uky.edu>
Sender: nobody@cornell.UUCP
Reply-To: ho@svax.cs.cornell.edu (Alex Ho)
Followup-To: comp.edu
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 25

In article <2601@ukecc.engr.uky.edu> wes@engr.uky.edu (Wes Morgan) writes:
>
>Why not teach machine organization concepts right alongside HLL programming?
>Certain topics, such as loop control and number crunching, could be programmed
>in both an HLL and in assembly.  This would give the beginning student both
>a better understanding of the machine and some rudimentary skills in assembly
>language.  Both of these would serve him well in future, more advanced machine
>organization courses.
>
last semester i completed a course similiar to what you describe
above. the second of a three semester sequence of "introduction 
to computer science" at u.c. berkeley, we were taught
1) programming in c; 2) programming in vax assembly; and 3) computer
architecture. the major programming project for the course was to
write a risc I simulator in c on the vax. what fun!
the goal of the course was exactly what you describe above. learn a hll
and machine architecture at the same time. it worked.

>Comments should go to comp.edu; I'm redirecting them there.
i hope it makes it there.

---

alex ho
university of california, berkeley             ho@svax.cs.cornell.edu     
a lost eecs major (spending the summer at)     cornell university