Comment #1 on issue 778 by anquetil...@gmail.com: FAMIXAssociation should not implement sourceAnchor http://code.google.com/p/moose-technology/issues/detail?id=778
not so sure.
When you have a big chunk of code, it can be used to find back in the code where an association comes from.
Exemple: verveineJ has an option to not export details of the classes (methods attributes). But, it still exports the dependencies between the classes that come from their methods and/or attributes (class A has x invocations to class B)
In this case, it is nice to have a sourceAnchor on the FamixAssociation to allow Moose to display the source code that created the associations