18 Mar
2009
18 Mar
'09
10:05 a.m.
My recommendation: do your stuff in your own package,
dont think
about the metadescriptions, you can integrate them later once your
model has settled. It will be easier.
I prefer this, but I might need them of the browser...
I will probably come back on this point soon.
Alexandre
Cheers,
Alexandre
On 17 Mar 2009, at 23:46, Tudor Girba wrote:
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Alex,
I saw that you removed FAMIXFunction from FAMIX-Core. Is there a
particular reason for this?
But, there is a larger issue here. FAMIX-Core is not meant to be
programmed, but instead it should be generate-able from the MSE
specification of FAMIX. So, basically a test should be to create
an MSE from the descriptions from FAMIX-Core and then regenerate
exactly the same classes back.
Like this, we can make sure that it remains portable and in sync
(via Fame) with implementations in other languages.
To deal with the implementation details, there is a Famix-
Implementation package.
Cheers,
Doru
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it
cannot be done."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev