Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!pwa-b!mmintl!franka
From: franka@mmintl.UUCP (Frank Adams)
Newsgroups: net.arch
Subject: Re: Using C as an aid to hand writing assembler
Message-ID: <1435@mmintl.UUCP>
Date: Fri, 9-May-86 16:20:55 EDT
Article-I.D.: mmintl.1435
Posted: Fri May  9 16:20:55 1986
Date-Received: Sun, 11-May-86 04:16:13 EDT
References: <817@harvard.UUCP> <Navajo.494> <460@cubsvax.UUCP>
Reply-To: franka@mmintl.UUCP (Frank Adams)
Organization: Multimate International, E. Hartford, CT
Lines: 17

In article <2336@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>	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,

Well, he shouldn't have.  Writing "pseudo-code" first (it needn't be
compilable or even in a well-defined language) is a standard design
technique, both for assembly code and for code in higher level languages.
In my experience, it is a lot more common than flow-chart writing.  Flow
charts are appropriate only for the rare program with an inherently very
complex flow of control.  In other words, if you find you need to write a
flow chart to get the logic right, you should first try to go back and
redesign the algorithm, or modularize it better.

Frank Adams                           ihnp4!philabs!pwa-b!mmintl!franka
Multimate International    52 Oakland Ave North    E. Hartford, CT 06108