Ok I will reintroduce (above below as next previous)
On Dec 16, 2008, at 2:59 PM, Tudor Girba wrote:
Hi Simon,
Yes, it is used just to specify the sequence of Associations as they appear in the code.
Not sure I get it (currently, we do nothing about it in the importer). Do you mean we can have for example: an Invocation after an Access after a Reference? It's ok then although it does not make sense for inheritance.
If it's about sequence, I prefer previous/next terms.
Makes sense.
As for above/below, we thought that a polymorphic message for source/target access at the Association level would help: from/to sounds good (overridden in subclasses to call accessor/variable, subclass/superclass, sender/receiver)
I suggest to do like we did for belongsTo. beglonsTo is now derived from the actual values. So, the values will still be stored in instance variables like accessor/variable, subclass/superclass, sender/receiver, and then from/to will return the values stored in these variables.
yes I will do that