I noticed that FAMIXEntity has a comments property that points to a collection of Strings. We should instead have a FAMIXComment entity that also has a sourceAnchor.
In my previous mail, I forgot to mention that FAMIXEntity already has a sourceAnchor variable, no need for the comment to have one therefore.
Speaking about source code, I guess that FAMIXSourceAnchor shoud be made abstract. Subclasses will particularize source location. As subclasses of FAMIXSourceAnchor, I see: - PharoAnchor: the code has to be accessible from the Pharo meta model (e.g., CompiledMethod>>getSource, ClassDescription>>definitionST80) - FileAnchor: a file stored on the hard disk. This class should have a beginIndex and endIndex to designate portion only
Easy to envision a SVNAnchor, SqueakSourceAnchor, ...
Everybody is fine with this proposal?
Cheers, Alexandre