Hi all,
Whats the best way to get LOC for nested FAMIXNamespaces? Lets say I'm looking at a FAMIX model of argouml. I used the "Infer Namespace Parents Based on Names" command in the Moose Panel.
I have a namespace argouml (org.argouml), and a namespace profile (org.argouml.profile). Calling numberOfLinesOfCode on the second namespace gives me a correct number of around 1000 (I assume because the "children" of profile are actually FAMIXClasses). Calling it on the first one returns 0.
So what would be the best way to get LOC on parent namespaces like "org", or "org.argouml"? Also is this by design that LOC does not get propagated up in the hierarchy or is it even a bug?
Cheers, Dennis
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
On Tue, Jul 24, 2012 at 2:34 PM, Dennis Schenk <[hidden email]> wrote: Hi all, I would do something like that in your namespace like "org":
self allRecursiveScopes sum: #numberOfLinesOfCode
Andre Hora _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Dennis Schenk
be careful that, in Java, packages are
not really nested.
This is contrary to intuition and there must be a reason for it, but that's how it is Look how Eclipse presents packages. Or notice that to use a.b.Class1 in a.b.c.Class2, you need to import it. nicolas On 24/07/12 14:34, Dennis Schenk wrote: Hi all, _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Andre Hora
That's working, thanks!
On Tue, Jul 24, 2012 at 3:14 PM, Andre Hora <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Nicolas Anquetil
Yes you are right. I have modeled java packages as being nested hierarchical so far. But the package "nesting" is actually just a way to organize files for the developer - which can be an interesting source of information too about a software system. It is not a strict hierarchy in the code though... will look into this...
On Tue, Jul 24, 2012 at 3:20 PM, Nicolas Anquetil <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |