18 May
2011
18 May
'11
9:59 a.m.
Hi,
this one bit me also, so I had a look at it.
It comes from declaration/initialisation of a class' field.
when this initialisation is the result of a method call, the caller is self, but the call
is outside a method.
so the question is how to represent that?
-> probably a fake method "<attribut-initialization>".
Now VerveineJ already has a fake method "<Initializer>" for the Java
initializer block. Do we use that one?
It makes sense and it avoids having too many fake things (which I am not very found of).
nicolas
----- Mail original -----
De: moose-technology(a)googlecode.com
À: moose-dev(a)iam.unibe.ch
Envoyé: Mardi 17 Mai 2011 01:20:08
Objet: [Moose-dev] Issue 629 in moose-technology: VerveineJ should not export implicit
variables without
parentBehaviouralEntity
Status: New
Owner: ----
CC: anquetil...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 629 by tudor.gi...(a)gmail.com: VerveineJ should not export
implicit variables without parentBehaviouralEntity
http://code.google.com/p/moose-technology/issues/detail?id=629
Some implicit variables are exported without a
parentBehaviouralEntity.
To reproduce it:
- download ArgoUML 0.28.1:
http://argouml-downloads.tigris.org/argouml-0.28.1/
- there are several instances (about 5-6 out of 2000+) of implicit
variables without parrentBehaviouralEntity
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev