21 Jan
2009
21 Jan
'09
10:10 p.m.
Hi,
Indeed this is correct. We knew this was a hack, and that is why we
tried to solve this in FAMIX 3.0.
Cheers,
Doru
On Jan 21, 2009, at 10:04 PM, Stéphane Ducasse wrote:
I do not remember but I guess that
the problem is that in famix2 there is no way to express class
references (class A refers to class B).
so we used that because if in your code you have
A>>foo
^ B zork
Now in FAMIX30 this is different.
You can have reference between classes.
Doru am I correct? I'm dead this evening.
Stef
On Jan 20, 2009, at 11:27 PM, Adrian DOZSA wrote:
--
www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting
is the right one."
Hi everybody,
Playing around with the FAMIX 2 specs and the LAN model I found
something very strange:
- I found an FAMIXAccess that accesses a FAMIXClass. According to
the FAMIX 2 meta-model and also the annotations from Moose the
accesses attribute of FAMIXAccess should be of type
FAMIXAbstractStructuralEntity. But the FAMIXAccess instance with id
71 from LAN model accesses a FAMIXClass
(Root::Smalltalk::LAN::LANInterface.initialize() ->
DependentList_class).
There are other examples too.
How were those accesses build? It is correct?
Thanks,
Adi D.
------------------------------
dipl.ing. Adrian DOZSA
Programming Engineer
mail: adi.dozsa(a)gmail.com
web: http://adi.dozsa.googlepages.com/
_______________________________________________
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