16 Feb
2010
16 Feb
'10
10:22 p.m.
I guess it should:) I will have a look at that tomorow.
2010/2/16 Johan Brichau <johan.brichau(a)uclouvain.be>
Hi Cyrill,
Should it not be added to the modifiers list? (I noticed that is where
#isAbstract is putting it) ?
If the loaded model is not a correct model, it's not really a good idea. Or
am I seeing that wrong?
On 16 Feb 2010, at 21:45, Cyrille Delaunay wrote:
----------------------------
Johan Brichau
johan.brichau(a)uclouvain.be
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
----------------------------
Johan Brichau
johan.brichau(a)uclouvain.be
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
The problem come from the method FAMIXMethod
>> kind: . In that method, a
test is made to be sure the value affected
correspond to list of kind
'allowed'. In that list, 'abstract' is not present (because it is no
more
used in famix3 I think). therefore , an error occure. For the moment, I had
'abstract' to this list of 'allowed' values. You should have this change
by
loading the last version of moose.
2010/2/16 Johan Brichau <johan.brichau(a)uclouvain.be>
now with my attachment... (sorry)
On 16 Feb 2010, at 20:50, Johan Brichau wrote:
> Hi guys,
>
> very cool!
> (Doru: sorry for not responding earlier. I only noticed your reply now)
>
> I just tried the attached mse file and got an error when the 'kind' of
a method was being set to 'abstract'.
>
> I'm trying to figure out how I can help to complete this. My first
guess
was to edit the MethodAttributesTraduction dictionary initialization
in the FM2TradInit method to correct that. However, what can the 'kind' be
in a Famix2 file? Since Famix3 has the same 'kind' attribute, I guess that
only the value 'abstract' should no longer be in there, right? Do you have
an example in the converter where that already occurs?
>
> cheers
> Johan
>
> On 16 Feb 2010, at 12:44, Cyrille Delaunay wrote:
>
>> Hello,
>> I join an example that works for me. But I think the problem could
come
from the head of your files, because I'm really not sure about how does
a famix2mse file begin with. Can you send me your files ?
>>
>> 2010/2/16 Tudor Girba <tudor.girba(a)gmail.com>
>> Nice initiative!
>>
>> However, I could not make it load any of my case studies. I get syntax
error. Could you provide an example that works?
>>
>> Cheers,
>> Doru
>>
>>
>>
>> On 16 Feb 2010, at 12:24, Simon Denier wrote:
>>
>>
>> On 16 févr. 2010, at 11:06, Laval Jannik wrote:
>>
>> Hi all,
>>
>> With Cyrille we work on a Famix2MseImporter in Pharo Famix3.
>>
>> It is a hack, in two parts:
>> First, we place a script between the parser and the MooseElement
creation. So this script switches elements of Famix2 to Famix3. For example,
a FAMIX.InheritanceDefinition in the Famix2Mse become a FamixInheritance in
Famix3.
>>
>> The other part of the script appears after the mooseModel creation. In
Famix3, there are FamixAccess and FamixReference. But in Famix2, there is
only FamixAccess.
>> FamixReference is for a target with type
FamixClass. But, when the
parser works, it is not easily possible to know the type
of an attribute.
So, to do it easy, when the MooseModel is created, we check all accesses and
test if the target is a FamixClass. If true, the script change the link in a
FamixReference.
>>
>> Now, we have three elements with no possible switch:
>> - there is no FAMIXGlobalVariable>>declaredType in Famix2.
>> - in Famix3, FAMIXInvocation>>receivingVariable has disappeared.
>>
>> I think this is replaced by FAMIXInvocation>>receiver
>>
>> - in Famix3, FAMIXParameter>>position has disappeared.
>>
>> The meta-informations in Famix2Mse are not taken account.
>>
>> Finally, this script is a hack, the aim is to provide a solution for
people who want to come to Pharo-Moose.
>>
>> You can load it with:
>>
>> Gofer new
>> squeaksource: 'Famix2Importer';
>> package: 'Famix2Importer';
>> load.
>>
>> A menu item is available in MoosePanel menu.
>> You can try it and mail us if you have some bugs.
>>
>> Cheers,
>> Jannik and Cyrille.
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow."
>>
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> <LAN sample
model-3.famix2.mse>_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
----------------------------
Johan Brichau
johan.brichau(a)uclouvain.be
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev