home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!usenet.ins.cwru.edu!cleveland.Freenet.Edu!cq184
- From: cq184@cleveland.Freenet.Edu (Spencer W. Hunter)
- Newsgroups: comp.lang.forth
- Subject: Re: CASE tools
- Date: 28 Jan 1993 10:29:21 GMT
- Organization: Case Western Reserve University, Cleveland, Ohio (USA)
- Lines: 29
- Message-ID: <1k8ci2INNa7f@usenet.INS.CWRU.Edu>
- NNTP-Posting-Host: hela.ins.cwru.edu
-
-
- mikeh@starnine.com (Mike Haas) writes:
-
- >Yes, one of the strong advantages I remember when I first came
- >to know Forth was that is was touted as promoting top-down
- >programming techniques due to it's extremely modular
- >architecture.
-
- : _THIS ." This " ;
- : _IS ." is " ;
- : _BOTTOM ." bottom-" ;
- : _UP ." up." ;
-
- : MAIN_PROGRAM _THIS _IS _BOTTOM _UP ;
- \ Main program is constructed from previously-defined words.
-
- Forth may be _designed_ top-down, but it's usually
- _constructed_ bottom-up. My implementation of the HOS compiler
- _begins_ with the main program declaration, and then proceeds
- to define what it will do through a successive breaking-down of
- functions which the compiler checks for correctness. By
- correctness, I mean that the control stuctures used are
- logically correct (yes, I know Forthies never make logic errors,
- but _I_ do, and they're often the trickiest bugs to track down).
- --
- +-------------------------------------+----------------------------------+
- | Spencer W. Hunter Tucson, Arizona | Veni, Vidi, Vamos. |
- | Internet: shunter@ccit.arizona.edu | They came, They saw, They left. |
- +-------------------------------------+----------------------------------+
-