22 Feb
2018
22 Feb
'18
10:24 a.m.
I beleive steph would like to have FAST-pharo, because FAST-core alone
does not do much, it's only the infrastructure.
I am working on making FAST-pharo loadable and passing all the tests
nicolas
On 21/02/2018 10:19, Cyril Ferlicot wrote:
On Wed, Feb 21, 2018 at 8:54 AM, Stéphane Ducasse
<stephane.ducasse(a)inria.fr> wrote:
--
Nicolas Anquetil
RMod team -- Inria Lille
Hi Stef,
You may want to use the CI image
https://ci.inria.fr/moose/job/FAST-On-Moose/
I cannot execute this image with the launcher.
And I cannot execute on my mac.
Hi!
At Synectique we depend on it with this snippet:
project: 'FASTCore'
with: [ spec
className: #ConfigurationOfFASTCore;
versionString: #development;
repository: 'http://smalltalkhub.com/mc/Moose/FASTCore/main/' ].
So, I think this should work:
Metacello new
repository: 'http://smalltalkhub.com/mc/Moose/FASTCore/main/';
configuration: 'FASTCore';
version: #development;
load
For the state of FAST: Fast meta model was not valid because it had
multiple opposites for some properties and in Moose 6 or 6.1 (I don't
remember) a model validation was added because MooseQuery require a
valide meta model.
With Nicolas we worked on it to make FASTCore valid. There was at the
top of the hierarchy a method #parentNode and multiple properties
defining it as opposite, which is not valid for FAME.
What we did is that instead of pointing #parentNode for multiple
properties, we created, for each property, a new opposite property in
the right subclass of FASTEntity and we reimplemented #parentNode to
point this new property. At the end, we replaced the #parentNode at
the top of the hierarchy by a subclass responsibility. To keep it was
only for backward compatibility.
We validated the changes with the tests of one of Synectique
meta-model. Maybe the implementations for the other languages are
still not valid but I did not had the knowledge nor the time to check
it :(