IMHO, parsing command-line options sounds a lot easier than it is.
Definitely use the modules unless you have a good reason for not doing
so. The author(s) of the module have probably already dealt with the
forehead-slappers that might not be obvious right off the bat, and it
will save you a lot
Ben Crane wrote:
>
> Hi all,
Hello,
> Sorry, should have added this to my last email. Does
> anyone know how to pass values to a perl script
> through the command line? Do you use param as in CGI
> scripting/
>
> I want a user to be able to specify certain parameters
> for the perl script (in c
On Dec 9, 2003, at 8:38 AM, Paul Kraus wrote:
[..]
Nameofperlscript command1 command2 command3
Params stored in global variable @ARGV
ben,
the alternative of course is to look into
perldoc Getopt::Long
where you can do many majical voodoo with...
Oh dear, just found my old DOG about getopt
You should use this: testscript.pl blah
where blah is the value to pass.
Ben Crane wrote:
Hi all,
Sorry, should have added this to my last email. Does
anyone know how to pass values to a perl script
through the command line? Do you use param as in CGI
scripting/
I want a user to be able to s
Nameofperlscript command1 command2 command3
Params stored in global variable @ARGV
> -Original Message-
> From: Ben Crane [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 09, 2003 11:23 AM
> To: [EMAIL PROTECTED]
> Subject: command line commands passed to perl scr
Hi all,
Sorry, should have added this to my last email. Does
anyone know how to pass values to a perl script
through the command line? Do you use param as in CGI
scripting/
I want a user to be able to specify certain parameters
for the perl script (in case they want to run an
overnight scheduler
