On Nov 16, 2007, at 23:57 PM, Adrian Kuhn wrote:
On 16 Nov 2007, at 15:35 , Toon Verwaest wrote:
What is the point of above/below in Association? The only thing I can think of is an extra abstraction for all those different types of "from/to" in the subclasses, but in that case the type and opposite seems very strange so I guess it's something else?
It is the source code order of invocations (the placement in association is incorrect, it should be pushed down to Invocation, as we do not want that for all associations).
I think that such information, in static analysis, is related to one behavioural entity: a List of ordered invocations --> a BehaviouralEntity (Method). So, Adrian, I suggest removing above/below and ensuring that the type of outgoingAccesses and of outgoingInvocations in BehaviouralEntity is List (the order should conform the order in the code)
Hani
AA
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev