Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Linking, Modules, and Overlays
Message-ID: <2674.UUL1.3#5129@willett.pgh.pa.us>
Date: 26 Apr 91 00:30:05 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 31


 Date: 04-19-91 (17:51)              Number: 1963 of 1988 (Echo)
   To: GARY SMITH                    Refer#: 1910
 From: RAY DUNCAN                      Read: NO
 Subj: LINKING, MODULES, AND OVE     Status: PUBLIC MESSAGE
 Conf: FORTH (58)                 Read Type: GENERAL (+)

   >LMI has something along those lines too, at least with their
   >"compiled to object code product" that is based on Tom Almy's work

 Two things are being mixed together here.  LMI has developed a
 translator that converts Forth source code to Intel/Microsoft 80x86 OMF,
 which can in turn be passed through the Linker (along with OBJ files
 from other languages such as C or MASM or ((God Forbid)) Fortran) to
 build an executable Forth kernel.  This is how our UR/FORTH products are
 built for DOS, OS/2, and 386 DOS Extender environments, and this object
 module compiler was written by LMI.

 Tom Almy's product is a native code compiler.  It translates high level
 Forth code directly to executable machine code (no threaded code
 involved anywhere, and no Linker needed).  We ship a version of this
 with our UR/FORTH systems, paying Tom a royalty, in addition to the
 object module compiler already described.

 NET/Mail : LMI Forth Board, Los Angeles, CA (213) 306-3530
 <<<>>>
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp