Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!mit-eddie!uw-beaver!cornell!rochester!pt.cs.cmu.edu!dsl.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Blocks vs Text files
Message-ID: <1823.UUL1.3#5129@willett.pgh.pa.us>
Date: 5 Oct 90 03:27:50 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 30


 Date: 10-01-90 (03:55)              Number: 3949 (Echo)
   To: DAVID BREEDING                Refer#: NONE
 From: DEAN MARTINDALE                 Read: NO
 Subj: BLOCKS AND FILES              Status: PUBLIC MESSAGE


 I have used blocks in Forth for quite a while, and thought they were the
 way to do it!--until I started using files. Now I consder blocks to be
 an outdated concept.

 A poorly designed program is a poorly designed program, whether written
 in files or in bocks. In readin several years of Forth Dimensions
 source code, I didn't notice any great legibility in the blocks
 jam-packed wit arcane Forth code. More often than not I would just skim
 over the code and not even try to understand it because it was a mess.(Please
fn
 F.D.! Some of the code was good, and you KNOW I'm talking abut yours!)

 I consider blocks to be excessively restrictive, while providing dubious
 advantages at best. In this day and age ofwidespread software crisis,
 we programmers need as few obstacles as possible in the development
 cycle.

 PCRelay:FORTHNET -> RelayNet (tm)

 NET/Mail : DC Information Exchange, MetroLink Int'l Hub.  (202)433-6639
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp