On Fri, Dec 28, 2007 at 08:09:23PM -0600, John M. Dlugosz wrote: > > >At present this isn't possible, the best we can offer is > >"/path/to/parrot/parrot /path/to/parrot/languages/perl6/perl6.pbc > >hello.pl", which is a pain. So, we need a way to package this up into a > >simple shell script, executable, or other item that can be placed in a > >PATH and executed directly. > > If I understand correctly, you want the parrot executable and the > perl6.pbc file to be somewhere on the PATH, and not coded into the shim > or otherwise configured at install time.
I don't mind if they're coded into the shim at install time, I just want something that "works" the way most end-users would expect to invoke a perl interpreter. > And putting parrot on the PATH > is not enough because it doesn't know to search for the .pbc file. Correct. > In the 4NT command shell under Windows, try this: > > set .pl=perl6 > alias perl6=parrot `"[EMAIL PROTECTED]"` > > The second line permits the use: > prompt> parrot hello.pl > > And the first further gives > prompt> hello.pl > or > prompt> hello This sounds like a potential solution for Windows users, but is it possible to create it so that this occurs somewhat "automatically" when perl6 is built or installed? Or do we have to tell people to execute the above commands whenever they want to run perl6? Also, I wouldn't want perl6 to (yet :-) usurp the .pl extension entirely -- I suspect people playing with perl6 will also have a few Perl 5 scripts lying about that they want to be invoked as Perl 5. Thanks! Pm
