Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!rutgers!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: <1873.UUL1.3#5129@willett.pgh.pa.us>
Date: 16 Oct 90 03:16:50 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 19


 Date: 10-07-90 (11:42)              Number: 3995 (Echo)
   To: DAVID BREEDING                Refer#: 3975
 From: MICHAEL HAM                     Read: NO
 Subj: BLOCKS AND FILES              Status: PUBLIC MESSAGE

 I know one programmer on the PC who writes in Forth with Sidekick loaded
 and uses Sidekick's memory-resident program as his program editor:  the
 code goes into text files edited with Sidekick, with the editor just a
 hot-key away.  One major advantage of blocks is the ability to reload a
 small portion of the application as one revises and debugs:  forgetting
 and reloading a single block is very quick compared to reloading a
 complete (long) file.  He gets around this difficulty by building his
 application as many short files, modularized as much as possible.

 NET/Mail : LMI Forth Board, Los Angeles, CA (213) 306-3530             
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp