Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

/usr/bin/env perl - query

by opensourcer (Monk)
on Oct 13, 2008 at 05:28 UTC ( #716740=perlquestion: print w/replies, xml ) Need Help??
opensourcer has asked for the wisdom of the Perl Monks concerning the following question:


what's the difference between /usr/bin/env perl and /usr/bin/perl.
suppose if the i have three differnt versions of perl who i switch between using /usr/bin/env perl, rather then mentioning the path in shebang.


Replies are listed 'Best First'.
Re: /usr/bin/env perl - query
by moritz (Cardinal) on Oct 13, 2008 at 05:36 UTC
    The main difference ist that /usr/bin/perl is a fixed path to one perl (which is usually the one that ships with your operating system), while /usr/bin/env perl will take the first perl in $PATH.

      I know it is OT, but ... does /usr/bin/env perl makes much sense at all? In this case, I could simply write perl. I feel that env is mainly useful when used together with options, such as env -i for providing an empty environment for a command...

      Ronald Fischer <>
        You are right that /usr/bin/env perl and perl will behave the same way on the command line. However, as JavaFan points out below, they are quite different when used on the shebang line (since the former will look for perl in your path, while the latter won't).
Re: /usr/bin/env perl - query
by toolic (Bishop) on Oct 13, 2008 at 14:07 UTC
Re: /usr/bin/env perl - query
by j1n3l0 (Friar) on Oct 13, 2008 at 08:46 UTC
    I've also noted that when you use:

    #! perl

    you cannot then run the program like this:


    Smoothie, smoothie, hundre prosent naturlig!
      And rightly so, assuming you're on Unix.

      On Unix, the first two bytes of an executable are "magical" - they tell the kernel what kind of executable it is. It may be a binary (depending on the OS, it may be able to run different styles of binaries), or it may be something that's to be fed to an interpreter. The magical bytes to signal that are 0x23 0x21, which in ASCII looks like "#!". Then the kernel takes the rest of the line (up to the next horizontal whitespace, or newline) as the name of the interpreter to run, and then feed the program as its input.

      So, if your program starts with

      #! perl
      and execute the program, the kernel will try to execute "perl" (assuming your OS skips leading whitespace; your program is more portable if it doesn't have whitespace after the #!). But the kernel isn't going to peek in your environment settings, and won't try all the directories in your $PATH. So it won't find "perl".

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: perlquestion [id://716740]
Approved by moritz
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (4)
As of 2017-12-11 05:40 GMT
Find Nodes?
    Voting Booth?
    What programming language do you hate the most?

    Results (286 votes). Check out past polls.