In fact, I modify "at the hand" the mse-famix2 to create a potential
It partially works.
But it is difficult to make it automatic, because the importer is define at the
Maybe it will be possible to make a hack but I don't know how.
The sole difficult of the "translation" (beside what I see) is Accesses which
are fork in Accesses and References in Famix3. But it is not a real difficulty.
I think it seams to be the easier way.
Or we can maintain the two versions, but I think it is not a good solution.
On Dec 3, 2009, at 12:23 , Tudor Girba wrote:
FAMIX 3.0 is not hooked in the VW Moose. What's more, in VW we work with Meta and not
The MSE that you get from VW won't parse as is in Pharo, because the Fame people
considered it a good thing to change the syntax. It's not nice, but there is not much
we can do about it.
So, to summarize, you get problems at two levels:
- FAMIX is not the same
- MSE is not quite the same (the difference is not that large, though)
I do not know what the right solution is.
On 28 Nov 2009, at 15:20, Laval Jannik wrote:
> Hi all,
> What is the state of Famix30 in VisualWorks ?
> I had a problem today:
> a guy ask to me how to use the DSM in VW.
> DSM is not updated in VW.
> I would like to propose to him to export as mse file. But I think that the mse file
is in Famix2.
> In pharo, we have Famix3.
> So, we should do a tool to make Famix3 with Famix2.
> Is it difficult to do this ? I think no, but my vision may be bad ?
> Jannik Laval
> PhD Student - Rmod Team - INRIA
> Certified Project Management Associate (IPMA)
> Moose-dev mailing list
"Presenting is storytelling."
Moose-dev mailing list