Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-pcd!hpcvca!charles
From: charles@hpcvca.CV.HP.COM (Charles Brown)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Dealing with multiple scripting languages (was: Elinating the 'rx' from AREXX)
Message-ID: <1410026@hpcvca.CV.HP.COM>
Date: 29 Aug 89 00:53:26 GMT
References: <1989Aug14.015608.21854@agate.berkeley.edu>
Organization: Hewlett-Packard Co., Corvallis, Oregon
Lines: 27

> 				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):

Oh joy!  A breath of fresh air!  This proposal takes the desirable
part of what was proposed earlier while nicely avoiding the pitfalls.

> /* $$SCRIPT(RX $*) */

> .key whatever
> ; $$SCRIPT(EXECUTE $*)

> # $$SCRIPT(BAWK -F: $*)

> %{
> /* $$SCRIPT(INSTANT-LEX $* S:MAIN.C)

> Peter "Have you hugged your wolf today" da Silva      `-_-'

Thank you Peter.
--
	Charles Brown	charles@cv.hp.com or charles%hpcvca@hplabs.hp.com
			or hplabs!hpcvca!charles or "Hey you!"
	Not representing my employer.