home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.programming
- Path: sparky!uunet!ukma!rsg1.er.usgs.gov!ornl!styx!jov
- From: jov@styx.ornl.gov (Judd Jones)
- Subject: Re: first-year programming languages
- Message-ID: <1992Nov13.212017.2603@ornl.gov>
- Summary: why not binary?
- Sender: usenet@ornl.gov (News poster)
- Organization: Oak Ridge National Lab
- References: <1992Nov9.152324.2715@jarvis.csri.toronto.edu> <wingo-111192171446@wingosmac.apple.com> <1992Nov13.171915.26423@cbnewsc.cb.att.com>
- Distribution: na
- Date: Fri, 13 Nov 1992 21:20:17 GMT
- Lines: 24
-
- In article <1992Nov13.171915.26423@cbnewsc.cb.att.com> bdewbank@cbnewsc.cb.att.com (bryan.d.ewbank) writes:
- >The first language in a computer science should be a machine language or
- >two. Perhaps a single-address machine, a double address machine, and
- >something "unusual".
-
- I wasn't going to say anything, but since you mention it...
-
- I used to help teach an intro to computing course for biologists.
- The students _started_ by writing a couple of very small programs
- in machine language (yep, in hex) using a small subset of the
- available instructions. Then a few more in assembler, looking
- at the listings, which show you what the assembler does. Then a few
- more in C, also looking at the listings, to see what the compiler
- does.
-
- The students ate it up. It was a real quick way to take the mystery
- out of it.
-
- #include "all_appropriate_disclaimers"
-
- judd jones -- oak ridge national lab -- jonesjp@ornl.gov
-
-
-
-