On Wed, 27 Jun 2007, Jasper Bryant-Greene wrote:
If you invoke via 'env', then you can use scripts which are themselves
interpreted as interpreters. e.g.
#!/usr/bin/env /home/johnc/foo/flashbang
Alas, for my (admittedly obscure) purposes... That puts the fix on the
wrong end. ie. I'd have to mod many scripts on many machines to use
env. I'm trying to put a wrapper around ruby so I can deliver a
pre-built version to all my colleagues, even those with outdated
versions of the dll's.
Sigh! It looks like it is just not going to work. Mayne with a tiny
statically linked C program... but I've run out of time for this
exercise. Sigh!
Alas I got out of the habit of using env when I found it didn't exist
on anything but linux. (One of those many little (ah yes, thats I hate
solaris/sco/irix/... !~ /linux/) moments.)
John Carter Phone : (64)(3) 358 6639
Tait Electronics Fax : (64)(3) 359 4632
PO Box 1645 Christchurch Email : [EMAIL PROTECTED]
New Zealand
