Jayesh Patel wrote:
So to make my script dummy proof, I am trying to find easy ways of parsing
the input the getopts ignores. I guess what I am looking for is a
getopt::std
that saves the part that it ignores in a special variable. Does anyone do
this ?
I don't like the getopt::long because
Never mind. I found that ARGUE has exactly what I'm looking for.
dumb mistake.
Thanks,
Jayesh
-Original Message-
From: Jayesh Patel
Sent: Thursday, January 30, 2003 7:59 PM
To: 'Wiggins d'Anconia'; Jayesh Patel
Cc: '[EMAIL PROTECTED]'
Subject: RE: getopt
-Original Message-
From: Wiggins d'Anconia [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 7:12 PM
To: Jayesh Patel
Cc: '[EMAIL PROTECTED]'
Subject: Re: getopt::std problem ignoring options
Jayesh Patel wrote:
> Hi all,
>
> Just wondering how
p.s. for those interested I have a cheat sheet I made a while ago at the
following (I am sure I will clean it up at some point and make it harder
to print ;-) but for now it is at least useful):
http://danconia.org/online/GetOpt_QuickRef.txt
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For add
Jayesh Patel wrote:
Hi all,
Just wondering how some of you are handling this issue that I have.
I am using the getopt::std. When I pass in parameters to my script with
a possible mistake, the getopts ignores the rest of my switches.
For example:
script.pl -a something -b something else
I am just a newbie here and this probably is not the best solution, but have
you considered placing the argument in quotes. It works for me.
script.pl -a something -b "something else" -c another_one -d etc
Kevin
From: Jayesh Patel <[EMAIL PROTECTED]>
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECT
> -Original Message-
> From: Jayesh Patel [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 31, 2003 8:15 AM
> To: '[EMAIL PROTECTED]'
> Subject: getopt::std problem ignoring options
>
>
> Hi all,
>
> Just wondering how some of you are handling this issue
> that I have.
> I am
