🚀 go-pugleaf

In article <1746@cs-spool.calgary.UUCP> deraadt@enme3.UUCP (Theo Deraadt) writes:
<I find this entire discussion rather silly; being as the Unix way is
<the most flexible. I mean, what part of the system knows better what
<shell interpreter a shell script should be run by, than the shell
<script file itself? Why not just use the #! syntax, and make the kernel
<know to follow the current system path.

I find this statement rather silly; being that just implementing the
Unix semantics would mean that both ARexx scripts and CLI scripts
wouldn't work at all. It would also eliminate the ability to use ARexx
as macro langauge in a properly designed shell, as opposed to an
interpreted programming language that gives you access to Execute().

You could solve the problem by making '#' a comment in all scripting
languages. This is rather ugly. You could also make the kernel skip
the first line, and start the script executing on the second line.
It's not clear that this will work for Rexx at all, and if it does,
you have to decide how sourceline() is going to deal with that first
line.  Both solutions also are hazardous to the portability of Rexx
scripts to other Rexx platforms, and neither deals with the loss of
ARexx as a macro langauge for your shell.

<I swear, some people just have a deathwish for all Unix semantics. Gad..

I swear, some people think Unix semantics are the solution to all
problems, even if these are problems that don't exist on Unix. Gad..

	<mike
--
ICUROK2C, ICUROK2.				Mike Meyer
ICUROK2C, ICWR2.				mwm@berkeley.edu
URAQT, I WANT U2.				ucbvax!mwm
OO2EZ, I WANT U2.				mwm@ucbjade.BITNET