Re^2: Perl wrapper

Thanks for the reply. That definitely solves the problem.

I just wish there was an easier way. I basically have to tell everyone at my company that they need to cut and paste this little piece of code at the top of their perl scripts. The "/bin/sh" at the top may be a bit confusing to them also.

Still, it's better than the alternative: Having to write a shell script every time you want to run a perl script (two files instead of one).

I wish /bin/env would just allow me to pass command line arguments to perl. Why can't it? And is there something like /bin/env that would?

Comment on Re^2: Perl wrapper

Replies are listed 'Best First'.
Re^3: Perl wrapper by ikegami (Patriarch) on Mar 16, 2011 at 18:12 UTC
just wish there was an easier way. We're constrained by your requirement to call the wrapper. I basically have to tell everyone at my company that they need to cut and paste this little piece of code at the top of their perl scripts. Still, it's better than the alternative: Having to write a shell script every time you want to run a perl script (two files instead of one). Neither are true. Both can be handled automatically during install. I wish /bin/env would just allow me to pass command line arguments to perl. Why can't it? Oh it does `$ /usr/bin/env perl -v This is perl 5, vers...` [download] The issue (Upd: with the shebang ) is that the OS passes everything after the first whitespace as one argument (Upd: to the command being launched ).	[reply] [d/l]
Re^4: Perl wrapper by weigand (Initiate) on Mar 16, 2011 at 19:22 UTC
Linux doesn't let you do that with "#! /usr/bin/env perl -v". It tries to find a file called "perl -v". Other OS's don't do that. I use linux primarily, so I can't do that. And the rest of your response was too cryptic and brief to be of much use I'm afraid. But thanks for the reply anyway.	[reply]
Re^5: Perl wrapper by ikegami (Patriarch) on Mar 16, 2011 at 20:01 UTC
You said "I wish /bin/env would just allow me to pass command line arguments to perl." Type in "`/usr/bin/env perl -v`" at the prompt and you'll see that it does. I don't know how I can say that any less "cryptic" or what additional words would help. Well, I added some anyway.	[reply] [d/l]