Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!ames!ucbcad!ucbvax!ucdavis!egg-id!ui3!dickow
From: dickow@ui3.UUCP
Newsgroups: comp.lang.forth
Subject: Re: DOS access
Message-ID: <460001@ui3.UUCP>
Date: Mon, 8-Dec-86 21:44:21 EST
Article-I.D.: ui3.460001
Posted: Mon Dec  8 21:44:21 1986
Date-Received: Mon, 15-Dec-86 23:40:33 EST
References: <3674@sdcc3.ucsd.EDU>
Organization: MRC, University of Idaho
Lines: 19

:

     I have used Forth for a few years, and never found it too "foreign"
when reading non-forth environment files. However, the Forth I have been
used to (Parsec Research's SuperForth64) has built in extensions that allow
reading and writing "ordinary" DOS formats. True, processing the data is
easiest using Block related words. Reading sequential data into a "temp-
orary" block, perhaps, although streaming shouldn't be too difficult either.
Forth should be ideal for setting up these kinds of processing.
    Incidentally, some systems even set up standard non-forth-block oriented
editors. This means you can edit with your word processor in a continuous
fassion, then compile later. Obviously this demonstrates Forth working with
non-system environments. The forth I am refering to is JForth, if youre
curious. It is out now for the Amiga. (See next basenote). JForth also
supports the usual block file structure.

---Bob Dickow       
---University of Idaho
egg-id!ui3!dickow