agreed
(except for the "simply create" :-) )
nicolas
On 11/14/2013 09:24 PM, moose-technology(a)googlecode.com wrote:
Comment #1 on issue 998 by tu...(a)tudorgirba.com: VerveineJ: Method in
EnumValue -> anonymous or inner class
http://code.google.com/p/moose-technology/issues/detail?id=998
Hmm, this situation should indeed be changed. The current model only
considers simple Enums. At the moment, EXCLUDE_BUGS will appear as an
EnumValue (which is a structural entity). I think this is good given that
we can have accesses to such enum values.
Now, the question is how to treat the initializer. Essentially, when we
have:
EXCLUDE_BUGS("property.excludebugs") {... }
it's kind of equivalent to something like:
private FilterKind EXCLUDE_BUGS = new FilterKind("property.excludebugs")
{ ... }
In this case, we can simply create a static initializer method entity for
the FAMIXEnum, and create the anonymous classes inside.
What do you think?
--
Nicolas Anquetil -- RMod research team (Inria)
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch