home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!bcm!rice!news.rice.edu!dens
- From: dens@flammulated.owlnet.rice.edu (Dennis Allen Schmitz)
- Newsgroups: comp.os.os2.apps
- Subject: Re: Self-Extracting Binaries dangerous? (Was: REXXShip: Self-Extracting UUEncode!)
- Message-ID: <DENS.92Sep8192745@flammulated.owlnet.rice.edu>
- Date: 9 Sep 1992 01:27:45 GMT
- References: <1992Sep6.175645.24543@midway.uchicago.edu>
- <DENS.92Sep8074930@sawwhet.owlnet.rice.edu>
- <1992Sep8.151847.10060@midway.uchicago.edu> <67843@hydra.gatech.EDU>
- Sender: news@rice.edu (News)
- Followup-To: comp.os.os2.apps
- Organization: Rice University, Houston, Texas
- Lines: 15
- In-Reply-To: gt1610c@prism.gatech.EDU's message of 8 Sep 92 21:44:18 GMT
-
- In article <67843@hydra.gatech.EDU> gt1610c@prism.gatech.EDU (MCGAUGH,MICHAEL KENNETH) writes:
-
- >It would be terrific, but, unless I'm mistaken, I'm forced to use
- >QUEUE statements, which prevents true xx-compatibility. If anyone has
- >any ideas on this, I'll be glad to do it for the next release.
-
- How about inncluding the xxencoded file in a comment at the top of the
- file then having the file process itself with linein. Might even be
- faster than using queue.
-
- Might also get speedup if can disable the process where the file gets
- 'compiled' into its EA's
-
- Later,
- den
-