Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site pyuxv.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!pyuxww!pyuxv!sr
From: sr@pyuxv.UUCP (S Radtke)
Newsgroups: net.arch
Subject: Re: Using C as an aid to hand writing assembler
Message-ID: <201@pyuxv.UUCP>
Date: Fri, 9-May-86 13:49:54 EDT
Article-I.D.: pyuxv.201
Posted: Fri May  9 13:49:54 1986
Date-Received: Sun, 11-May-86 15:54:17 EDT
References: <817@harvard.UUCP> <Navajo.494> <460@cubsvax.UUCP>
Reply-To: sr@pyuxv.UUCP (25220-S Radtke)
Organization: Bell Communications Research, Piscataway, NJ
Lines: 20
Summary: Executable specs in C for assembly code


>	Some years ago when I was learning 6800 assembler (anybody remember
>D2 kits?) I used to first write everything in C and then hand compile it
>into M6800 asm.  When I told my professor (are you reading this Professor
>Efe?) that I did this instead of drawing flow-charts, he laughed at me, but
>as long as you keep your code simple, the conversion is trivial and can be
>done in your head as fast as you can write down the asm code.  Perhaps the
>...

I just read an article from IEEE Transactions on Software Engineering
Feb.,1986 by Peter Henderson, "Functional Programming, Formal Specification,
and Rapid Prototyping". Except for the hand compilation,
which could be avoided, you were doing a similar thing- using a high level
language as a formal specification for a lower level language. Your code
was an executable specification and allowed rapid prototyping to influence
the design decisions at an early point.

Steve Radtke
Bell Communications Research
Piscataway, NJ