Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!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: <1822.UUL1.3#5129@willett.pgh.pa.us>
Date: 5 Oct 90 03:27:48 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 25


 Date: 09-26-90 (00:25)              Number: 3856 (Echo)
   To: CHARLIE HITSELBERGER          Refer#: 3855
 From: DAVID BREEDING                  Read: 09-26-90 (11:23)
 Subj: BLOCKS AND FILES              Status: PUBLIC MESSAGE

 Actually, the way F83 handles blocks vs files is the best I've found. 
 That is, it allows you to open files that are subdivided into 1k blocks.
 That way you use blocks still, but you've got files you can open, edit,
 and move around just like any other file.

 However, back to the original argument.  C. Moore picked blocks for 2
 reasons, one they are divided into equal 1k blocks (which makes them
 easy to find, print, and colate), and it is a way to insure consise
 programming.  When people use editors they tend to run all over the
 place, starting 2 orr3 spaces over, commnets in different places, ect. 
 With blocks you have a set structure which you can not change, therefore
 everything looks pretty much the same.  I think blocks are GREAT!! 
 Anyone who has ever looked through a 20 page Forth editor file can
 attest to the fact that they are A LOT harder to follow...

 Nuff said...
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp