Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-tgr!tgr!jcm@ornl-msr.ARPA
From: jcm@ornl-msr.ARPA (James A. Mullens)
Newsgroups: net.lang.c
Subject: C Programming style - writing code
Message-ID: <256@brl-tgr.ARPA>
Date: Mon, 29-Jul-85 12:40:29 EDT
Article-I.D.: brl-tgr.256
Posted: Mon Jul 29 12:40:29 1985
Date-Received: Wed, 31-Jul-85 04:18:51 EDT
Sender: news@brl-tgr.ARPA
Lines: 12

How do people write code now-a-days??
I haven't used paper much since I've gotten some full-screen editors.  This has
made me a top-down code designer since I tend to use skeleton functions as
I write and fill them in later.  Something I haven't seen other people mention -
Since using c (somewhat) and pascal (a lot), I find I spend much more time
designing the data structures (pointers, data types, arrays, files, etc) than
designing the actual code.  Or rather, I think in terms of the data and when
I'm finished designing it, writing the code "around it" is straightforward
(even boring and trivial at times).  Years ago, when I only programmed in FORTRN,
the importance and usefulness of data structures would not have occurred to me.
Now I debate arrays vs linked lists vs trees.  Say! This is boring and trivial
at times also (:-)!! - Jim Mullens