Path: utzoo!utgpu!watmath!iuvax!mailrus!uflorida!sun.ufnet.ufl.edu!misterx From: misterx@sun.ufnet.ufl.edu ( ) Newsgroups: comp.sys.amiga.tech Subject: Re: Dealing with multiple scripting languages (was: Elinating the 'rx' from AREXX) Message-ID: <20754@uflorida.cis.ufl.EDU> Date: 17 Aug 89 18:55:18 GMT References: <1989Aug14.015608.21854@agate.berkeley.edu> <1410024@hpcvca.CV.HP.COM> Reply-To: misterx@sun.ufnet.ufl.edu ( ) Organization: UFNET Lines: 22 In article <1410024@hpcvca.CV.HP.COM> charles@hpcvca.CV.HP.COM (Charles Brown) writes: >Devine was correct, at least for some Unices. Under HP-UX, #!/bin/csh >is interpreted by exec before csh OR sh sees it. The convention you >describe (comment first -> /bin/csh, else /bin/sh) is older and is >obsolete. I don't know if HP-UX inherited this behaviour from AT&T or should read "... is older and unfortunately not obsolete." :-) >from BSD. (HP-UX tries to take the best of both.) > Charles Brown charles@cv.hp.com or charles%hpcvca@hplabs.hp.com > or hplabs!hpcvca!charles or "Hey you!" Well, I looked at some code, and it does seem that Devin was correct, the default action on BSD machines for the loader which does not find a magic cookie, is to pass the file to /bin/sh, sh then will decide what to do with it. /bin/sh decides by looking at the first line. -- "One, you lock the target. Two, you bait the line. Three, you slowly spread the net. And four, you catch the man." UUCP: ...!gatech!uflorida!sun.ufnet.ufl.edu!misterx Internet: misterx@sun.ufnet.ufl.edu | vishnu@pine.circa.ufl.edu