If you got fancy you could embed that tonenized data into an EXE, have the EXE allocate that tokenized data into memory, then pass that memory to RexxStart() allong with the command line parms... that is pretty much be what an Object Rexx EXE would be.
--
Michael Lueck
Lueck Data Systems
Remove the upper case letters NOSPAM to contact me directly.
You can use Mark Hessling's rexx/wrapper to create an executable which has
the rexx code compiled in to it. If your goal is to improve performance
by compiling into machine code, this won't help, but if the goal is to
have a single executable which includes rexx code, it can be helpful.
http://rexxwrapper.sourceforge.net
--
Patrick TJ McPhee
East York Canada
pt...@interlog.com
"RKR" <iH...@Spam.com> wrote in message
news:ao6pj9$hds$1...@ausnews.austin.ibm.com...
"Mark Yudkin" <myu...@compuserve.com> wrote in message
news:aobamv$45q$1...@nntp-m01.news.aol.com...
"RKR" <iH...@Spam.com> wrote in message
news:aoh868$6rk$1...@ausnews.austin.ibm.com...
Keep in mind that does not produce an EXE, it tokenizes the source so people can't see it / steal your code.
RexxC myProg.rex myProgTok.rex <-- Tokenize
Rexx myProgTok.rex <-- Execute
Now, Rexx is merely a kick-start EXE to read in the source file and pass it off to the DLL. What I was saying above is either you can build your own EXE, or try out RexxWrapper which I had forgotten about, to build a program that is basically Rexx.exe + myProgTok.rex all in one file.
"Michael Lueck" <Nmlu...@SlueckPdataAsystemsM.com> wrote in message
news:3DAE8FD5...@SlueckPdataAsystemsM.com...