Re: GEOS file format, assembly, etc.

Billy Tanksley <tanksley@fallbrook.csusm.edu>
Errors-To: brian@grot.starconn.com
Date: Tue, 1 Feb 94 12:46 PST
Message-id: <Pine.3.05a.9402011116.B15193-a100000@fallbrook.csusm.edu>
X-Comment: Zoomer PDA List
Originator: zoomer-list@grot.starconn.com
Errors-To: brian@grot.starconn.com
Reply-To: <zoomer-list@grot.starconn.com>
Sender: zoomer-list@grot.starconn.com
X-Listserv-Version: 5.5 -- Copyright (c) 1991/92, Anastasios Kotsikonas
From: Billy Tanksley <tanksley@fallbrook.csusm.edu>
To: Multiple recipients of list <zoomer-list@grot.starconn.com>
Subject: Re: GEOS file format, assembly, etc.
Status: OR


On Mon, 31 Jan 1994, Peter Dudley wrote:

> Read the VM files chapter.  The file structure is not a structure so much
> as a set of indirections and handle tables, with the data stored throughout.
> You'll see that it's very much a nontrivial task creating a GEOS VM file
> from outside GEOS.

I got an answer here-- the info is in the file Internal/geosStr.def .  It
certainly will not be trivial, but on the other hand, I will only do it
once, and then my Forth language will be able to do it itself.
 
> Pete.
> 
Great thanks to all who helped and are helping me.

-Billy
GeoForth is a little closer and still freeware.