What's the best way to test existence of arguments

[pgodfrin]

Greetings,

Is there a better way to test for existence of arguments besides
$#ARGV ? I have a little program that uses -s via the getopts module,
and if that option is used I want to force an argument. I suppose I
could use getopts(s - but I wondered if there is another "clean" way
to do that?

pg

 

[Joost Diepenmaat]

Greetings,

Is there a better way to test for existence of arguments besides
$#ARGV ? I have a little program that uses -s via the getopts module,
and if that option is used I want to force an argument. I suppose I
could use getopts(s - but I wondered if there is another "clean" way
to do that?

GetOpt::Long should give you all the control you'd need, including
default values, types and real named options and readable variable
names. It's a bit more verbose than GetOpt, but IMO it's also more
readable and definitely more flexible.

Joost.

 

[Jürgen Exner]

Is there a better way to test for existence of arguments besides
$#ARGV ?

What about using @ARGV in scalar context?
if (! @ARGV) {
#I got no command line arguments
}

jue

 

[pgodfrin]

What about using @ARGV in scalar context?
if (! @ARGV) {
#I got no command line arguments
}

jue

doy - I'm a nitwit...
thanks,
pg

 

[Ben Morrow]

Is there a better way to test for existence of arguments besides
$#ARGV ?

I would use @ARGV in scalar context rather than $#ARGV, but what's wrong
with that?

@ARGV or die "You need an argument!\n";

seems pretty clear to me.

I have a little program that uses -s via the getopts module,
and if that option is used I want to force an argument. I suppose I
could use getopts(s

....or indeed that?

Ben

 

[Michele Dondi]

Is there a better way to test for existence of arguments besides
$#ARGV ? I have a little program that uses -s via the getopts module,

@ARGV


Michele

 

[Ilya Zakharevich]

[A complimentary Cc of this posting was sent to
Joost Diepenmaat

GetOpt::Long should give you all the control you'd need, including
default values, types and real named options and readable variable
names. It's a bit more verbose than GetOpt, but IMO it's also more
readable and definitely more flexible.

Do not know as now, but a couple of years ago ::Long had some
limitations which ::Std did not. (I started a rewrite, but did not
finish it.)

Hope this helps,
Ilya