Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!um-math!sharkey!cfctech!teemc!hpftc!zardoz!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!usc!apple!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!ucbvax!agate!eris.berkeley.edu!mwm From: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) Newsgroups: comp.sys.amiga.tech Subject: Re: Dealing with multiple scripting languages (was: Elinating the 'rx' from AREXX) Message-ID: <1989Aug29.233027.4285@agate.uucp> Date: 29 Aug 89 23:30:27 GMT References: <1989Aug14.015608.21854@agate.berkeley.edu> <1410026@hpcvca.CV.HP.COM> Sender: usenet@agate.uucp (USENET Administrator;;;;ZU44) Reply-To: mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) Organization: Missionaria Phonibalonica Lines: 46 In article <1410026@hpcvca.CV.HP.COM> charles@hpcvca.CV.HP.COM (Charles Brown) writes: <> All scripting languages worth their salt <> have some sort of comment syntax. So, make some unique pattern that can be <> used to identify a script language, and allow it anywhere in the first couple <> of lines of the script (in the first couple of lines to allow for programs <> that use a seperate line to indicate a comment pseudo-op, or need some magic <> on line 1): <