Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re: Passing parameters to scripts

by moxliukas (Curate)
on Aug 12, 2002 at 11:16 UTC ( #189441=note: print w/replies, xml ) Need Help??

in reply to Passing parameters to scripts

All command line parameters are stored in @ARGV array. So you can access it directly like:

my $file = $ARGV[0];

or even like this (modifying the array):

my $file = shift @ARGV;

However if you need only to pass a file name as a parameter for opening it at a later stage, you can say

while(<>) { }

straight away and this will read from the file on the command line.

If you want to pass complex things on the command line (like options, etc), have a look at a module Getopt::Long

And no, I don't think there is any difference in Unix and Windows in this respect.

Just my 2 Lithuanian cents.

Replies are listed 'Best First'.
Re: Re: Passing parameters to scripts
by demerphq (Chancellor) on Aug 12, 2002 at 11:45 UTC
    There are differences in how the various shells interpret certain symbols, so what you may need to use for one shell might not work in another. For instance in *nix arguments are normally globbed by the OS, wheras in Win32 they are normally globbed by the program. Other difference would be quoting characters and escape rules.

    Yves / DeMerphq
    Software Engineering is Programming when you can't. -- E. W. Dijkstra (RIP)

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://189441]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (5)
As of 2018-07-18 18:54 GMT
Find Nodes?
    Voting Booth?
    It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?

    Results (393 votes). Check out past polls.