Not only, they are used, I think, also in the MoosePanel. And if you want to generate a tool that can be used for different metamodel, as MooseQuery or OrionGenerator, you need the pragmas.
<multivalued> and <derived> also.
We are currently working with Pavel to define more easily metamodels without pragmas and FMMultivalueLink.
Anne
Le 20 janv. 2017 à 15:18, Alexandre Bergel alexandre.bergel@me.com a écrit :
Really?
Does it mean that the pragmas contained in:
FAMIXType>>subInheritances <MSEProperty: #subInheritances type: #FAMIXInheritance opposite: #superclass> <multivalued> <derived> <MSEComment: 'Subinheritance relationships, i.e. known subclasses of this type.'>
^subInheritances
Are only for the import / export? <multivalued>, <derived> ?
Alexandre
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Jan 20, 2017, at 7:24 AM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
Pragmas are only useful when you want to export/import. They are also used a bit for navigation but that use can be easily replaced with dedicated inspector panes. So, if you do not have the import/export use case, you do not need the pragmas.
Cheers, Doru
On Jan 19, 2017, at 11:06 PM, Nicolas Anquetil Nicolas.Anquetil@inria.fr wrote:
+1
On 19/01/2017 18:37, Alexandre Bergel wrote:
As a bit off the topic, I have always questioned myself to using pragmas. Are pragmas a mechanism we should continue to have to define a meta-model? Most of the time, I am better at implementing a simple meta-model without famix at all than trying to understand pragmas.
Alexandre
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Jan 19, 2017, at 8:23 AM, Anne Etien anne.etien@univ-lille1.fr wrote:
Hi,
I am developing a tool based on Fame pragma. Considering the following methods: FAMIXSQLExpression >>referencedRequests <MSEProperty: #referencedRequests type: #FAMIXRequest opposite: #usedInExpression> <multivalued> <MSEComment: 'List of requests referenced by the expression.'> ^ referencedRequests
FAMIXRequest >>usedInExpression <MSEProperty: #usedInExpression type: #FAMIXSQLExpression opposite: #referencedRequests> <MSEComment: 'Expression in which the request is used.'> ^ usedInExpression
(FAMIXSQLExpression mooseDescription at: 'referencedRequests') hasOpposite should return true. However, I don’t have always the same behavior after each resetMeta. (1 to: 100) do: [ : e | MooseModel resetMeta. (FAMIXSQLExpression mooseDescription at: 'referencedRequests') hasOpposite ifFalse: [ 1halt ] ]. always halts, at some unpredictable iteration (usually less than 10)
Does someone has any idea what is the problem and how to solve it?
By the way, MooseSQL is available here https://ci.inria.fr/moose/job/MooseSQL/
Thanks in advance for your help.
Anne
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- Nicolas Anquetil -- MCF (HDR) Project-Team RMod
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- www.tudorgirba.com www.feenk.com
“The smaller and more pervasive the hardware becomes, the more physical the software gets."
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev