Hi,

On 18 May 2011, at 09:59, Nicolas Anquetil wrote:

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).

Thanks for looking into this. I like this solution.

Cheers, Doru

nicolas

----- Mail original -----

...

De: moose-technology@googlecode.com À: moose-dev@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...@gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ

New issue 629 by tudor.gi...@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

---

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

-- www.tudorgirba.com

"Some battles are better lost than fought."

Updates: Labels: Milestone-4.5

Comment #2 on issue 629 by tudor.gi...@gmail.com: VerveineJ should not export implicit variables without parentBehaviouralEntity http://code.google.com/p/moose-technology/issues/detail?id=629

Cool. I tested it on ArgoUML and it works fine.