Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!PITTVMS.BITNET!LEFF
From: LEFF@PITTVMS.BITNET
Newsgroups: comp.lang.forth
Subject: Re: File handling tips
Message-ID: <8903271451.AA07855@jade.berkeley.edu>
Date: 25 Mar 89 01:38:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Forth Interest Group International List <FIGI-L%SCFVM.bitnet@jade.berkeley.edu>
Organization: The Internet
Lines: 15

In BLAZIN' FORTH both data and words are kept on fixed
length blocks--obviously some storage space is wasted
but there is a certain elegance to the idea--multiple
screens can be kept in the traditional block buffers
and each can be edited and re-compiled in a flash.  I've
never been able to write a word longer than a standard block--my
blocks usually hold between 2 to 10 words in a certain "theme."
My system allows me to allocate 0 to about 30 data and
program blocks for very easy access.  The disadvantage
of the block system is the unorthodox use of the disk
media--the disk directory shows NO files present on the
Commodore system. Also, if you want to transfer a set of
blocks you have to write them into a sequential ASCII file.
Perhaps its old fashioned, but I've always enjoyed the
block/buffer system.