Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!lll-winken!ames!pacbell!sactoh0!tree!stever
From: stever@tree.uucp (Steve Rudek)
Newsgroups: comp.lang.forth
Subject: Re: FORTH Modules: current confusion?
Summary: What is F83s?
Keywords: modules; dictionary structure; compiler mods
Message-ID: <1989Dec18.203626.8810@tree.uucp>
Date: 18 Dec 89 20:36:26 GMT
References: <5596@sdcc6.ucsd.edu> <6708@tank.uchicago.edu> <15058@well.UUCP>
Organization: TREE BBS (916)349-0385 Sacramento, Ca
Lines: 14

In article <15058@well.UUCP>, jax@well.UUCP (Jack J. Woehr) writes:
> 	Further, in F83S and FPC the dictionary headers are
                ^^^^
What is this?  That is, how does it differ from plain "F83".  Does anyone 
know if F83 is a "tiny" model program with code and data intermixed in the
same segment?  I know it is a "com" file but it is my understanding that
a com program may be "small" and not "tiny".  The reason I ask is it pertains
to my interest in porting F83 to Xenix 386.  I'm wondering if I could just
replace the DOS calls with Xenix system calls and then change the metacompiler
to spit out a hex listing of everything over "100 hex".  Then I could
transport that file to xenix and relatively easily prepend a header...and it
might work...?
-- 
{pacbell!sactoh0! OR ucdavis!csusac!}tree!stever