Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!sat!farren
From: farren@sat.com (Michael J. Farren)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: How to improve Workbench 2.0!
Message-ID: <1991Feb23.203358.27835@sat.com>
Date: 23 Feb 91 20:33:58 GMT
References: <1991Feb11.113601.1338@sugar.hackercorp.com> <9474@uwm.edu> <8659@gollum.twg.com>
Organization: SAT
Lines: 30

david@twg.com writes:
[on UNIX methods of doing scripts]
>the first line is read and examined to see if it is like so:
>
>	#! /path/interpreter args
>
>And if so, then /path/interpreter is executed with the file on its stdin.
>[...]
>There is a small problem of backwards compatibility with AREXX scripts.
>That is, there is/was a convention that you start 'em with "/* comment */"

So where's the problem?  You just look for the following, in order:

1. Does it start with a "/* ... */" comment?  If so, run it under AREXX,
   if possible.  If not, abort.

2. Does it start with the UNIX standard "#! <filename>" comment line?
   If so, execute <filename> <this script as argument>.  If anything
   goes wrong, abort.

3. If it doesn't start with either one, try it as a standard AmigaDOS
   script.

I don't see why all alternatives can't be comprehended in this fashion.

-- 
+-----------------------------------------------------------------------+
| Michael J. Farren                                      farren@sat.com |
|                        He's moody, but he's cute.                     |
+-----------------------------------------------------------------------+