Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!wuarchive!texbell!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: Dealing with multiple scripting languages (was: Elinating the 'rx' from AREXX) Message-ID: <4117@sugar.hackercorp.com> Date: 16 Aug 89 11:30:40 GMT References: <1989Aug8.214011.3351@agate.berkeley.edu> <1989Aug14.015608.21854@agate.berkeley.edu> Organization: Sugar Land Unix - Houston Lines: 21 In article <1989Aug14.015608.21854@agate.berkeley.edu>, mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) writes: > Several questions remain: like 1) can we make this cover enough of the > current ways of finding a program, and 2) can we do this "fast > enough." If the command interpreter has to be loaded from disk, check if it's OK, and then pass it to the next... it'd be tolerable for a hard disk and too slow for floppies. 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. Alternatively, there is already a mechanism for doing this in Workbench. It uses a seperate ".info" file. Maybe something like that would be acceptable for shells... maybe even using the same file? -- Peter "Have you hugged your wolf today" da Silva `-_-' ...texbell!sugar!peter, or peter@sugar.hackercorp.com 'U`