Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!psuvax1!wuarchive!gem.mps.ohio-state.edu!apple!agate!ucbvax!VMTECMEX.BITNET!EM302723
From: EM302723@VMTECMEX.BITNET ("Mario Camou R. ", Dr. Mangagoras)
Newsgroups: comp.lang.icon
Subject: Icon executables?
Message-ID: <8910140111.AA06348@megaron.arizona.edu>
Date: 14 Oct 89 01:43:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 19
X-Unparsable-Date: Fri, 13 Oct 89 09:28:33 MEX

OK...so you wouldn't get much of a speed gain by directly compiling to machine
code.
 
However, that brings up another idea. Seems to me that to have a directly
executable Icon program would be a real help in production systems (whether
internal use or for external distribution). An idea would be to put an option
on ICONT so that ICONX is linked together with the program. That way you would
get executable programs without modifying ICONT or ICONX too much.
 
Of course, I'm just speaking from the top of my head. How's this sound, feasi-
bility-wise?
 
+----------------------------------+------------------------------+
|  Dr. Mangagoras                  | Mario Camou Riveroll         |
|  EM302723@VMTECMEX.BITNET        | Apdo. Postal 41554           |
|                                  | Mexico, D.F. 11001 Mexico    |
+----------------------------------+------------------------------+
| Don't take life too seriously - it's just a temporary situation |
+-----------------------------------------------------------------+