Mailing-List: contact dev-help@click.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@click.apache.org
Message-ID: <17710855.28031277333810332.JavaMail.jira@thor>
Date: Wed, 23 Jun 2010 18:56:50 -0400 (EDT)
From: "Bob Schellink (JIRA)" <jira@apache.org>
To: dev@click.apache.org
Subject: [jira] Commented: (CLK-696) Use typesafe collection
In-Reply-To: <5795767.60701276797863421.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLK-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881940#action_12881940 ] 

Bob Schellink commented on CLK-696:
-----------------------------------

I'm not sure the cost outweighs the benefit. The OptionOrGroup feels awkward to me especially the OptionGroupi#getValue method. What do others think?

> Use typesafe collection
> -----------------------
>
>                 Key: CLK-696
>                 URL: https://issues.apache.org/jira/browse/CLK-696
>             Project: Click
>          Issue Type: Improvement
>          Components: core, extras
>            Reporter: Finn Bock
>            Assignee: Finn Bock
>            Priority: Minor
>         Attachments: typesafe-select.patch
>
>
> In CLK-633, the API was upgraded to use type safe collections. The remaining internal parts of Click should also be upgraded.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.