Hi all,
It crossed my mind that we could do this, but I rejected it since it's
not really helpful. The #! line is generally only applicable to UNIX-y systems. Even on those systems that do support it, the path to Parrot won't always be the same either.
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. My 2 cents... Karl Forner
