Issue 569 in moose-technology: EnumValue should be a StructuralEntity

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 569 in moose-technology: EnumValue should be a StructuralEntity

moose-technology
Status: New
Owner: [hidden email]
Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.4

New issue 569 by [hidden email]: EnumValue should be a  
StructuralEntity
http://code.google.com/p/moose-technology/issues/detail?id=569

 From Nicolas:

Why is EnumValue not a StructuralEntity ? (it is a NamedEntity)

 From http://download.oracle.com/javase/tutorial/java/javaOO/enum.html
"An enum type is a type whose fields consist of a fixed set of constants."

they are considered fields in Java ...

I just realized Verveine does not export access to enumValues.
But with the meta-model I have (bare 4.3), it seems an access to an  
enumValue is an invocation.

This is counter intuitive.


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 569 in moose-technology: EnumValue should be a StructuralEntity

moose-technology
Updates:
        Status: Duplicate
        Mergedinto: 568

Comment #1 on issue 569 by [hidden email]: EnumValue should be a  
StructuralEntity
http://code.google.com/p/moose-technology/issues/detail?id=569

(No comment was entered for this change.)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev