Does it currently hurt us anywhere or is this just a pure
architectural discussion? If the latter, I vote to keep the class as
"Enum".
Ciao
Henning
On Wed, Jan 21, 2009 at 09:09, Louis Ryan <[email protected]> wrote:
> The fact that the class is called Enum in Shindig is an implementation
> detail and certainly isn't required to match anything in the protocol or
> standardized JS API. Its not a true Java enum because its designed to allow
> for arbitrary extension. How about 'ExtensibleEnum;' ?
>
> On Tue, Jan 20, 2009 at 5:53 PM, Kevin Brown (JIRA) <[email protected]> wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/SHINDIG-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665681#action_12665681]
>>
>> Kevin Brown commented on SHINDIG-878:
>> -------------------------------------
>>
>> The big problem is that "Enum" is in java.lang, not so much the naming
>> itself. Naming a class enum is a lot like naming a class "String" in the
>> annoyance department.
>>
>> Changing the OS spec because of a java language aspect doesn't make any
>> sense at all, though admittedly the bit of the OS spec that defines "Enum"
>> is bad design in and of itself.
>>
>> > Please rename org.apache.shindig.social.opensocial.model.Enum
>> > -------------------------------------------------------------
>> >
>> > Key: SHINDIG-878
>> > URL: https://issues.apache.org/jira/browse/SHINDIG-878
>> > Project: Shindig
>> > Issue Type: Improvement
>> > Components: Common Components (Java)
>> > Reporter: Jordan Zimmerman
>> >
>> > Enum is a very bad choice for a class name as it clashes with the JDK
>> class with the same name. Please rename
>> org.apache.shindig.social.opensocial.model.Enum
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
