Issue 629 in moose-technology: VerveineJ should not export implicit variables without parentBehaviouralEntity

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

Issue 629 in moose-technology: VerveineJ should not export implicit variables without parentBehaviouralEntity

moose-technology
Status: New
Owner: ----
CC: [hidden email]
Labels: Type-Defect Priority-Medium Component-VerveineJ

New issue 629 by [hidden email]: 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 629 in moose-technology: VerveineJ should not export implicit variables without parentBehaviouralEntity

Nicolas Anquetil
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: [hidden email]
> À: [hidden email]
> 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: [hidden email]
> Labels: Type-Defect Priority-Medium Component-VerveineJ
>
> New issue 629 by [hidden email]: 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
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
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 629 in moose-technology: VerveineJ should not export implicit variables without parentBehaviouralEntity

Tudor Girba
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: [hidden email]
>> À: [hidden email]
>> 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: [hidden email]
>> Labels: Type-Defect Priority-Medium Component-VerveineJ
>>
>> New issue 629 by [hidden email]: 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
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Some battles are better lost than fought."




_______________________________________________
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 629 in moose-technology: VerveineJ should not export implicit variables without parentBehaviouralEntity

moose-technology
In reply to this post by moose-technology
Updates:
        Status: Fixed

Comment #1 on issue 629 by [hidden email]: VerveineJ should not  
export implicit variables without parentBehaviouralEntity
http://code.google.com/p/moose-technology/issues/detail?id=629

(No comment was entered for this change.)

_______________________________________________
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 629 in moose-technology: VerveineJ should not export implicit variables without parentBehaviouralEntity

moose-technology
Updates:
        Labels: Milestone-4.5

Comment #2 on issue 629 by [hidden email]: 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.

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