1 Apr
2009
1 Apr
'09
5 p.m.
On 1 avr. 09, at 16:51, Alexandre Bergel wrote:
I like the idea of having a way to customize the link
to source
code. However, no idea whether this should be in FAMIX. Maybe not.
In that case, FAMIXSourceAnchor may be renamed as MooseSourceAnchor ?
That's an idea. Indeed, the primary use is to be able to browse the
source code from the Moose Browser. However, perhaps some people would
like to use Famix with an external tool, performing some complementary
analysis on source code, without relying on MooseEntity and co. And
perhaps there is too much hypothesis in the previous sentence to make
this proposition interesting :)
Cheers,
Alexandre
On 1 Apr 2009, at 16:30, Simon Denier wrote:
--
Simon
I just stumble upon the case when adding
Famix.SourceAnchor to the
metamodel. It does not make much sense to make SourceAnchor a
subclass of FamixEntity.
Yet a common way to 'get' the Famix metamodel (found here and there
in the code) is to use FAMIXEntity withAllSubclasses (which misses
SourceAnchor)
Yet another way is to use PackageInfo, but then I need to know all
packages in which Famix extensions have been defined.
Any suggestion?
Note: we dont have this problem with MooseModel, because MooseModel
uses MooseEntity withAllSubclasses :)
but I dont want to always have this dependency on Moose when
loading Famix alone
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev