Hi, from/to are derived properties and they should describe the association. For example:
FAMIXAccess>> from ^ self accessor FAMIXAccess>> to ^ self variable next/previous denote the position of the association in the code with respect to the other associations. For example, imagine this Pharo code: self doSomething. self doSomethingElse. you will get two FAMIXInvocations, and these can be linked through the previous property (next is derived). Does this make sense? Btw, these questions are better suited for the Moose mailing list: http://www.moosetechnology.org/#twitter Cheers, Doru On Mon, Jun 22, 2015 at 5:06 PM, abdelghani ALIDRA <alidran...@yahoo.fr> wrote: > Hi everybody, > > when working with the FAMIX meta model, one must implement the previous, > next, from and to methods for each class extending FAMIXAssosiation. > What is the diffence between previous/from and next/to? > if I make > MyFamixClass>>from > ^previous > the same information is displayed twice in the Moose panel (because both > methods are annotated with the MSEProperty in the superclass) > Who can one avoid that? > > Regards > > Abdelghani > -- www.tudorgirba.com "Every thing has its own flow"
