Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!accuvax.nwu.edu!tank!uwvax!astroatc!nicmad!madnix!rat
From: rat@madnix.UUCP (David Douthitt)
Newsgroups: comp.lang.forth
Subject: Re: File handling tips
Message-ID: <590@madnix.UUCP>
Date: 2 Apr 89 16:39:10 GMT
Reply-To: rat@madnix.UUCP (David Douthitt)
Distribution: na
Organization: ARP Software, Madison, WI
Lines: 29


David Phillip Oster (oster@dewey.soe.berkeley.edu.UUCP) writes:
|
| One advantage of traditional "blocks" over files:
| 
| When your program crashes during LOAD, it is easier to fix it up and
| continue, rather than FORGETing everything and restarting the load:

This is not necessarily so.  Why not put the blocks into files?
I believe that the Macintosh MacForth does this - I know Mad Apple Forth does.
This way, everything still looks like blocks to the user, but can either
be a standard text file or an "all-text" file just like the blocks are.

| Since Forth is a postfix language, the only reasonable way of pretty
| printing is to make the structures line up on the RIGHT edge, not the LEFT
| as in prefix languages:

     [... stuff deleted ...]

I would disagree - but then no one follows my style of indentation anyway.
I have my form and you have yours.

      [david]

-- 
======== David Douthitt :::: Madison, WI :::: The Stainless Steel Rat ========
FidoNet: 1:121/2 ::::: WittiNet: "Curiouser and curiouser, said Alice." ::::::
UseNet:  ...{rutgers|ucbvax|harvard}!uwvax!astroatc!nicmad!madnix!rat
ArpaNet: madnix!rat@cs.wisc.edu        {decvax|att}!