home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.apps
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uchinews!ellis!sip1
- From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
- Subject: Re: Self-Extracting Binaries dangerous? (Was: REXXShip: Self-Extracting UUEncode!)
- Message-ID: <1992Sep8.224909.5218@midway.uchicago.edu>
- Sender: news@uchinews.uchicago.edu (News System)
- Reply-To: sip1@midway.uchicago.edu
- Organization: Dept. of Econ., Univ. of Chicago
- References: <DENS.92Sep8074930@sawwhet.owlnet.rice.edu> <1992Sep8.151847.10060@midway.uchicago.edu> <67843@hydra.gatech.EDU>
- Date: Tue, 8 Sep 1992 22:49:09 GMT
- Lines: 22
-
- 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.
- >Doesn't REXX have a command for reading its own source code?
- >If it does, why not use that and then keep the xx-compatibility.
- >Since REXX isn't compiled, you can put any garbage you want in
- >the source and it doesn't matter as long as the interpreter never
- >sees the junk. Have the first line of REXX code jump to the end
- >of the file, where the uncompress code is. Then have the uncompress
- >code read the source code in between, which happens to be the
- >xx-compatible encoded information.
-
- This sort of feature is under very active consideration for the next
- version of REXXShip, although the precise method of implementation is
- still up in the air.
-
- --
- Timothy F. Sipples | The OS/2 FREQ. ASKED QUESTIONS LIST is avail. from
- sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/faq.
- Dept. of Econ., Univ. | Or from LISTSERV@BLEKUL11.BITNET (send "HELP").
- of Chicago, 60637 | Family Values Means a Job
-