Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!rochester!pt.cs.cmu.edu!LINDENTHAL.CAE.RI.CMU.EDU!jwb
From: jwb@LINDENTHAL.CAE.RI.CMU.EDU (John Baugh)
Newsgroups: comp.misc
Subject: Re: Defining structure (Was: The "evil" GOTO)
Message-ID: <5020@pt.cs.cmu.edu>
Date: 18 May 89 13:36:50 GMT
References: <24330@agate.BERKELEY.EDU> <13765@lanl.gov> <142@quad.uucp>
Organization: Carnegie-Mellon University, CS/RI
Lines: 23

In article <142@quad.uucp> dts@quad.uucp (David T. Sandberg) writes:
>In article <13765@lanl.gov> jlg@lanl.gov (Jim Giles) writes:
>>}>(Definitions -  structured: code developed by stepwise refinement using
>>}>(ultimately) whatever low-level programming tools that are available.
>
>Question: your definition of structured programming actually sounds
>closer to modular programming to me.  Please reference a source
>which defines structured programming in this fashion.

  "This naturally suggests that programs should be developed by 
beginning at a high level of abstraction and repeatedly refining the 
level of detail.  This approach, often call structured programming,
top-down programming, or programming by stepwise refinement, ...
  "More precisely, we will say that a program is structured when it 
reveals a variety of levels of detail to the reader, and we will reserve 
the term top-down for the process of creating such a program by proceeding
from the abstract to the concrete."

                         From John Reynolds, _The_Craft_of_Programming_
                                

John Baugh

--