[Mono-dev] Mono.GetOptions Option Bundles

Almann T. Goo almann.goo at gmail.com
Fri May 5 13:15:23 EDT 2006

On 5/5/06, Rafael Teixeira <monoman at gmail.com> wrote:

> Nothing mandates that you use the standard bundle as the basis, you
> can create your own with just the needed options. The down side is
> that some functionality would have to be duplicated in that case.

With the current architecture, I am not sure how one would do this--short of
copying the Options, OptionList, and OptionDetails class and modifying them
slightly.  From what I've seen, OptionList and OptionDetails are tied to the
Options class.  The problem is that I can't sub-class Options without
inheriting those non-virtual standard options.

The interface idea keeps with the declarative approach and maintains source
compatibility.  Of course this would make for ABI/API changes so they
wouldn't be allowed in the current version.

Oh, and on a separate note, I've noticed that invalid options come through
as arguments (even before a "--" argument).  Is this by design?  Is there a
way to overload or customize this behavior?

Thanks again!

Almann T. Goo
almann.goo at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060505/02851574/attachment.html 

More information about the Mono-devel-list mailing list