Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re^2: The basics

by Joost (Canon)
on Jun 24, 2006 at 19:17 UTC ( #557400=note: print w/ replies, xml ) Need Help??


in reply to Re: The basics
in thread The basics

The #! line has two programs that "interpret" it:

  • To the shell. An executable file that starts with a #! line will cause the executing shell to start up the program indicated in that line. That way, you can use #!/bin/sh to create a shell script, #!/usr/bin/perl to create a perl script etc. At least on unixish systems, there is always a shell involved in this process (but for instance windows doesn't work like that)

  • (Possibly) to the interpreter indicated in the #! line.

    For instance, perl reads the additional arguments on the #! line as a sort of "setup parameters". Example: #!/usr/bin/perl -wT will run perl with global warnings enabled and in taint mode.


Comment on Re^2: The basics
Download Code
(OT) Re^3: The basics
by Hue-Bond (Priest) on Jun 24, 2006 at 21:59 UTC
    To the shell. [...] At least on unixish systems, there is always a shell involved in this process

    The #! line, also called shebang, tells nothing to any shell. It's the kernel who interprets it. When the first two bytes of an executable file are #!, the kernel runs the command that follows them, with the parameters specified, and feeds it the whole file on its standard input:

    $ cat > a #!/usr/bin/tail -n2 1 2 3 4 5 6 7 ^D $ chmod +x a $ ./a 6 7 $ strace ./a 2>&1 | grep -c sh 0

    --
    David Serrano

      Just FYI: That is only true for recent Unix versions. Originally, the #! line was interpretted (only) by the shell(s).

      - tye        

      I'm trying to figure out where you get the idea that the contents are passed to tail's stdin. It's not. The full path to the file (as given by the shell - full path if searched via PATH, relative path if PATH not used) is passed in.

      Compare the output of "strace ./a" and "strace /usr/bin/tail -n2 < a". The former has a call to "open" and all reading is done from filehandle 3. The latter doesn't call open, and all reading is done from filehandle 0.

        I'm trying to figure out where you get the idea that the contents are passed to tail's stdin.

        I guess I'll also have to. To my surprise, you're right.

        --
        David Serrano

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://557400]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (13)
As of 2014-12-19 13:07 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (82 votes), past polls