Hi,

On Thu, Nov 14, 2013 at 10:09 PM, Nicolas Anquetil <Nicolas.Anquetil@inria.fr> wrote:

I think it should be kept open
- first, it is trivial to change how VerveineJ name the anonymous classes

- second, it would be good that verveineJ and Moose agree on this point.

unless we decide to change the default name in Moose (in that case I would be for changing it accordingly in verveineJ)

Perhaps I did not understand the issue then. The anonymous classes are called: 'Class.method(ParameterType)::anonymous(AnotherParameterType)

Why do you say there is a mismatch between Moose and VerveineJ? Is it because of the code in isAnonymousClass? If yes, then there is really no problem. The extra conditions in there are for inFamix and inFusion, not for VerveineJ.

Try this on any model:

model allTypes select: [:each | (each name beginsWith: 'anonymous') and: [each isAnonymousClass not] ]

and you will see that you will get an empty collection.

Or did I get something wrong?

Doru

nicoals

On 11/14/2013 09:25 PM, moose-technology@googlecode.com wrote:

Comment #5 on issue 999 by tu...@tudorgirba.com: VerveineJ: management of the anonymous class
http://code.google.com/p/moose-technology/issues/detail?id=999

The thing inside the brackets is the type of the parameter, I think. In any case, do we agree to close the issue and tackle the Enum one separately?

--

Nicolas Anquetil -- RMod research team (Inria)

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

www.tudorgirba.com

"Every thing has its own flow"