22 Dec
2010
22 Dec
'10
9:16 p.m.
----- Mail original -----
De: "Tudor Girba"
<tudor.girba(a)gmail.com>
À: "Nicolas Anquetil" <Nicolas.Anquetil(a)inria.fr>
Cc: "Moose-dev Moose Dev" <moose-dev(a)iam.unibe.ch>
Envoyé: Mercredi 22 Décembre 2010 12:00:28
Objet: Re: Request to Join Project Verveine J
Hi Nicolas,
Thanks for getting me access to the project. I will try to look into
it in the following year.
next is a derived property. You should only save the previous pointer.
yes, but FAMIXAssociation>>previous: calls FAMIXAssociation>>next: which does
not exist.
So the question remains: Is it supposed to work?
As this seems to be a pretty basic thing lacking here ...
The context of next/previous is the context of the
scope in which the
association is defined. Thus, for example, for invocations, the scope
is the sender method. For inheritance, the scope is the class.
OK for the invocation and access and reference.
But What would mean a next/previous for inheritance? Is it only for multiple inheritance?
nicolas