Apparently when applying blindly the changes of
oscar I broke FAMIX2
(argh)
so I will take another image and check one by one the suggested
changes and produce a new Famx20 package
Stef
On Sep 4, 2008, at 11:40 AM, Tudor Girba wrote:
Hi Stef,
I know it breaks. The errors that you mention are due to the fact
that
some old classes from VW do not conform to Fame.
That is why I said that for the moment just put there
FAMIX2ModelRoot
and then I will take a look at the code in the afternoon.
Cheers,
Doru
On Sep 4, 2008, at 11:26 AM, Stéphane Ducasse wrote:
On Sep 4, 2008, at 11:15 AM, Tudor Girba wrote:
> Hi,
>
> FAMIX2Class mooseDescription works only if the repository is
> correctly
> setup :).
>
> If you look in the code, then "MooseModel>>meta" is the one that
> returns the meta-model.
Ah
I thought that we could plug any metamodel under fame
Now I did
MooseModel2 class>>metaTower
"self resetMetaDescriptions. self metaTower"
| pp |
^metaTower ifNil: [
pp := FMPragmaProcessor new.
pp queue: MooseEntity withAllSubclasses.
pp run.
metaTower := pp asTower]
and I got a wonderful error which is a bad smell to me.
Stef
> It is lazily created and in the current
> implementation is starts the lookup from FAMIXEntity which does
> not
> include FAMIX2.
>
> I would suggest to make it FAMIX2ModelRoot for the moment just to
> make
> it work with your code.
>
>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
www.tudorgirba.com/blog
"What we can governs what we wish."
_______________________________________________
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