[ANN] MooseQuery

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[ANN] MooseQuery

Anne Etien
Hi,

MooseQuery has been integrated in the Moose 6.0 (Thanks Vincent!). Normally, it works on Pharo and Java Famix model. If you want to be able to use MooseQuery on any other language, you have to add new pragmas in the ‘annotations' class method of the famix entities.

Please notice that currently, as previously announced, MooseQuery has not the same behavior than MooseChef concerning the method extensions.

Considering classA having a method methodA1 calling a method methodBExt1 that extends classB.
classB is defined in pckgB and its extension method by pckgC.
Considering the two following requests:
1. classA queryOutgoingInvocation atClassScope atPackageScope  
2. classA queryOutgoingInvocation atPackageScope                        

To the first query, MooseChef and MooseQuery answer the same: pckgB
To the second query, MooseChef answers pckgC and MooseQuery answers pckgB and pckgC.

After discussion with some people here in Lille, it is difficult to remain generic (as it is the purpose of MooseQuery) and to manage this specific case where the owner of a method can be either a package or a class.

I tried to lock Stéphane in his office and force him to discuss with me about this issue and have a look at the code, but until now he succeeds to escape ;o)

If you have any question or feedback please feel free to share.

Anne
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] MooseQuery

Blondeau Vincent
Thanks Anne,

I would like to add that the ConfigurationOfMoose is now editable with Versionner.
For this, I created specific configurations for PetitMSE, DynaMoose, and Arki to not be dependent directly of packages commited on other repositories than the Moose one, and, I defined the groups Core and Test in a way that the tests are executed by the "moosetests" command line.

It seems that nothing is broken because there is more tests than before!

Cheers,
Vincent

> -----Message d'origine-----
> De : [hidden email] [mailto:moose-dev-
> [hidden email]] De la part de Anne Etien
> Envoyé : jeudi 8 octobre 2015 17:04
> À : Moose-related development
> Objet : [Moose-dev] [ANN] MooseQuery
>
> Hi,
>
> MooseQuery has been integrated in the Moose 6.0 (Thanks Vincent!).
> Normally, it works on Pharo and Java Famix model. If you want to be able to
> use MooseQuery on any other language, you have to add new pragmas in
> the 'annotations' class method of the famix entities.
>
> Please notice that currently, as previously announced, MooseQuery has not
> the same behavior than MooseChef concerning the method extensions.
>
> Considering classA having a method methodA1 calling a method
> methodBExt1 that extends classB.
> classB is defined in pckgB and its extension method by pckgC.
> Considering the two following requests:
> 1. classA queryOutgoingInvocation atClassScope atPackageScope
> 2. classA queryOutgoingInvocation atPackageScope
>
> To the first query, MooseChef and MooseQuery answer the same: pckgB To
> the second query, MooseChef answers pckgC and MooseQuery answers
> pckgB and pckgC.
>
> After discussion with some people here in Lille, it is difficult to remain generic
> (as it is the purpose of MooseQuery) and to manage this specific case where
> the owner of a method can be either a package or a class.
>
> I tried to lock Stéphane in his office and force him to discuss with me about
> this issue and have a look at the code, but until now he succeeds to escape
> ;o)
>
> If you have any question or feedback please feel free to share.
>
> Anne
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev