Le 15/10/2017 à 19:53, Nicolas Anquetil a écrit :
Hi,
I could not find any queryAllOutgoing (on a moose5 image, I " lost" my
computer last week, and did not recover it fully yet, so no recent moose
image).
Did you mean queryAllOutgoingDependencies ?
Hi,
No. #queryAll{Direction} was introduced in Moose 6 with MooseQuery.
If so:
- queryStaticOutgoingAssociations, returns all association that can be
statically resolved in Pharo, i.e. Accesses, references, and inheritances
- queryAllOutgoingInvocations is quite obvious. Note that in pharo they
cannot be resolved statically (hence the candidates field of the
invocations)
- queryAllOutgoingAssociations, is a combination of all associations:
the "static" ones + invocations
This is the goal of #queryAll{Direction}
- finally, queryAllOutgoingDependencies, gathers all
dependencies, even
those not modeled as associations: for exemple, the declaredType of the
variables and the functions
So each one of these return a different thing
For the un-efficient implementation to query all the in/out
associations, it seems like a good idea to improve it.
However, I would advocate against introducing new traits in Moose.
Traits tie us very much to Pharo. This is a problem if we plan to move
moose models to gemstone for example...
My solution will not introduce new Trait to Moose. Also if we use
Gemstone I think we will win more time by changing Metacello to flatten
Trait in Gemstone during the loading than to remove Traits.
nicolas
--
Cyril Ferlicot
https://ferlicot.fr
http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France