Section 5.3.  The Invocation Arguments

Table of Contents

5.3. The Invocation Arguments

Technically, the diamond operator isn't looking at the invocation argumentsit works from the @ARGV array. This array is a special array preset by the Perl interpreter as the list of the invocation arguments. In other words, this is like any other array, (except for its funny, all caps name), but when your program starts, @ARGV is already stuffed full of the list of invocation arguments.[Section 5.3.  The Invocation Arguments]

[Section 5.3.  The Invocation Arguments] C programmers may be wondering about argc(there isn't one in Perl), and what happened to the program's own name (that's found in Perl's special variable $0, not @ARGV). Depending upon how you've invoked your program, there may be a little more happening than we say here. See the perlrun manpage for the full details.

You can use @ARGV like any other array; you can shift items off of it or use foreach to iterate over it. You could even check to see if any arguments start with a hyphen, so you could process them as invocation options (like Perl does with its own -w option).[Dagger;]

[Dagger;] If you need more than one or two such options, you should almost certainly use a module to process them in a standard way. See the documentation for the Getopt::Long and Getopt::Std modules, which are part of the standard distribution.

The diamond operator looks in @ARGV to determine what filenames it should use. If it finds an empty list, it uses the standard input stream; otherwise, it uses the list of files that it finds. This means that after your program starts and before you start using the diamond, you've got a chance to tinker with @ARGV. For example, here we can process three specific files regardless of what the user chose on the command line:

    @ARGV = qw# larry moe curly #;  # force these three files to be read
    while (<>) {
      print "It was $_ that I saw in some stooge-like file!\n";

    Table of Contents
    © 2000- NIV