Hi,
Muchly delayed reply, sorry.
Karl Forner wrote:
Just a little trick that can help. If the parrot interpreter in in
your path, you can workaround
the need to specify the aboslute path by using the env command. For
instance:
#! /usr/bin/env parrot
I used that trick to enable the use of perl scripts in a
multi-platform but shared filesystem environment.
Nice trick, but even so it's still UNIX-y platform specific, which was
my main concern; much more than the "different locations on platforms
where it does work" issue.
Thanks,
Jonathan
