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: Metacompilation
Message-ID: <1900.UUL1.3#5129@willett.pgh.pa.us>
Date: 22 Oct 90 00:58:08 GMT
Organization: String, Scotch tape, and Paperclips.  (in Pgh, PA)
Lines: 27


   To: RAY DUNCAN                    Refer#: NONE
 From: SHANNON VANCE                   Read: 10-19-90 (18:22)
 Subj: METACOMPILER                  Status: PUBLIC MESSAGE
 Thanks for the speedy reply. 
 I don't really have anything specific in mind for the DOS command. It
 just seems that this capability would be used for special circumstances.
 I forgot to mention that we need to be able to specify the path for
 intermediate files (.img and .sym) if they are to be directed to another
 path by previous compiles. In other words, if a compile puts it's 
 .img and .sym files in a seperate directory from the input file, the
 subsequent compile needs to know where to find these files.
 I consider being able to test environment variables to be of secondary
 importance to using them. As for usage; if they could be freely usable
 as any group of characters, they could be, in effect, a macro that is
 defined at the operating system level.
 As for the ^brk problem. We have clones. Always have. We have many
 different styles: Everex, Milex, etc. They are connected to a Novell
 LAN. All of them crash when trying to abort from compiles.
 By the way, have you seen JForth by Delta Research? It is a remarkable
 accomplishment. They are in San Rafael, and mainly support the Amiga.
 Thats about all. Thanks again, Shannon Vance

 NET/Mail : LMI Forth Board, Los Angeles, CA (213) 306-3530             
-----
This message came from GEnie via willett through a semi-automated process.
Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp