On Sun, Aug 01, 2010 at 02:51:10PM +0100, Lucian Branescu wrote: > 2010/8/1 Alberto Simões <[email protected]>: > > > > > > On 01/08/2010 14:34, Vasily Chekalkin wrote: > >>>> Does it have any disadvantage to set it from "#! perl" to > >>>> "#!/usr/bin/perl"? > >>>> > >>>> Also: "#! parrot" -> "#!/usr/bin/parrot" > >>>> > >>>> This is my favorite. > >>> > >>> Surely the #! for perl should be the path of the perl used to run > >>> Configure.pl, > >>> and the #! for parrot be the path parrot will be installed to? > >>> > >>> /usr/bin/perl and /usr/bin/parrot may not even exist. > >> > >> Indeed. What about "#!/usr/bin/env perl"? I'm not sure how it works on > >> Windows. > > > > I really never understood how this one works :-| > > I thought that was the canonical way to do it. All python scripts I've > ever seen had #!/usr/bin/env python. It's the option most likely to > run everywhere.
Agree for the general case, where just that script is going to be copied onto a "foriegn" machine that one knows nothing about. But in this case, we're already running on the target machine, and we're writing out files to run on *it*, so we can do better. Nicholas Clark _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
