Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!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: FORTH FOR 8-bit COMMODORE
Message-ID: <1760.UUL1.3#5129@willett.pgh.pa.us>
Date: 19 Sep 90 03:12:08 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 27


 Date: 09-16-90 (22:32)              Number: 3791 (Echo)
   To: CHARLIE HITSELBERGER          Refer#: 3754
 From: DAVID BREEDING                  Read: NO
 Subj: 128 COMMORDORE FORTH          Status: PUBLIC MESSAGE

 Actually F83 does allow you to switch drives, however running all of the
 devices together, as you suggested, is really bad.  If you've ever tried
 to find a small program in a full disk of BForth, then you know what a 
 pain it can be.  Actually my idea is this...allow you to set up a file, 
 like 'DavesForth.txt' and set the number of blocks you want to use.  Say
 something like ' 5 create davesforth.txt' would create a file that is 5 
 blocks (1k blocks just like Starting Forth) long.  You could also add to
 the file later like...'2 addblock'

 This is actually the way CP/M F83 for the C128 handles it, and it works
 very, very well.  It also allows you to easily create and handle data
 files from within forth.  No messy ML routines or lack of porability.  I 
 think it creates a situation where you have the best of both worlds,
 files and blocks.

 When can I see your file, and what format is it in.  I have Merlin 128
 so I would prefer that, however I'm flexible.  Let me know, I'll be
 waiting...
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: uunet!willett!dwp or dwp@willett.pgh.pa.us