GetoptLong bug?

[Daniel Berger]

Hi all,

Ruby 1.8.2
Solaris 9 and Windows XP Pro

If I have this:

# opt_test.rb
require "getoptlong"

opts = GetoptLong.new(
["--test", "-t", GetoptLong::REQUIRED_ARGUMENT]
)

puts "Done"

And then I run this:

ruby opt_test.rb

or this:

ruby opt_test.rb -t

Shouldn't a MissingArgument error be raised in both cases?

Regards,

Dan

 

[ts]

D> opts = GetoptLong.new(
D> ["--test", "-t", GetoptLong::REQUIRED_ARGUMENT]
D> )

This mean that if you give the option --test then an argument is required,
but it will not give an error if -t is not given.

D> puts "Done"

Now you don't try to retrieve the options, this is why it don't give an
error in this case :

call #each_option (or #get) and it will give the error.

 

[Stefan Lang]

Hi all,

Ruby 1.8.2
Solaris 9 and Windows XP Pro

If I have this:

# opt_test.rb
require "getoptlong"

opts = GetoptLong.new(
["--test", "-t", GetoptLong::REQUIRED_ARGUMENT]
)

Try to insert this:

opts.each { |opt, value|
puts "#{opt} has value #{value}"
}

 

[Daniel Berger]

D> opts = GetoptLong.new(
D> ["--test", "-t", GetoptLong::REQUIRED_ARGUMENT]
D> )

This mean that if you give the option --test then an argument is required,
but it will not give an error if -t is not given.

D> puts "Done"

Now you don't try to retrieve the options, this is why it don't give an
error in this case :

call #each_option (or #get) and it will give the error.

Ah, I thought there was a way to force it to choke before this.
Thanks.

Dan