From: Kirill Shutemov <k.shutemov@...>
Date: 2005-05-23T18:10:50+09:00
Subject: Re: options parsing: required and conflict

------=_Part_11727_22358488.1116839447506
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

> I'd had similar idea in the early days, but abandoned it soon.
> As those relations could come complicated easily, it didn't
> feel worth to design/learn a such "mini-language" again. We
> have already the powerful enough language.

What about add to OptionsParser method 'usage':

opts =3D OptionParser.new{|opts|
<skip/>
opts.usage("--operation1 [--optional_option] --required_option ARG=20
[--optional_option2 ARG]")
opts.usage("--operation2 [--optional_option] --required_option2=20
[--optional_option3 ARG]")
<and_so_on/>
}

I tried to do it by myself, but optparse.rb is too difficult for me :(

------=_Part_11727_22358488.1116839447506--