Article View: comp.sys.amiga.tech
Article #916Re: Dealing with multiple scripting languages (was: Elinating the 'rx' from AREXX)
From: Bernie Cosell
Date: Wed, 16 Aug 1989 12:45
Date: Wed, 16 Aug 1989 12:45
16 lines
1332 bytes
1332 bytes
In article <4117@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: }The solution of using a #!-type flag followed bvy the name of the command }interpreter is a good idea, but it can't be the first couple of bytes in }the file since the different programs out there use different comment }conventions. Having some sort of flag on the first line, however, would }help. Actually, the OS could just set up the file pointer to the script file to be _just_past_ the first line, so that the comment conventions of the particular program would be irrelevant. There's no reason I can see why the newly-spawned child process's standard input must be set to the *beginning* of the script file, when the OS knows that the first line is actually control info. /Bernie\
Technical Details
Message-ID:
<44364@bbn.COM>Path:
arc1-ca.pugleaf.net!utzoo!attcan!utgpu!watmath!iuvax!mailrus!bbn!bbn.com!cosellReferences:
<1989Aug8.214011.3351@agate.berkeley.edu> <1989Aug14.015608.21854@agate.berkeley.edu> <4117@sugar.hackercorp.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!watmath!iuvax!mailrus!bbn!bbn.com!cosell From: cosell@bbn.com (Bernie Cosell) Newsgroups: comp.sys.amiga.tech Subject: Re: Dealing with multiple scripting languages (was: Elinating the 'rx' from AREXX) Message-ID: <44364@bbn.COM> Date: 16 Aug 89 12:45:05 GMT References: <1989Aug8.214011.3351@agate.berkeley.edu> <1989Aug14.015608.21854@agate.berkeley.edu> <4117@sugar.hackercorp.com> Reply-To: cosell@BBN.COM (Bernie Cosell) Organization: Bolt Beranek and Newman Inc., Cambridge MA Lines: 16