Hi Doru,
So it's FAMIX!
I can take care of fixing that.
Cheers,
M.
2014-05-09 21:03 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>om>:
Hi,
superclass simply takes one of the super FAMIXClass objects. It would
indeed be better if we would take the first FAMIXClass that is not
interface.
I am offline until next week. Can someone else look into this?
Doru
On Tue, May 6, 2014 at 2:05 AM, Mircea Filip Lungu <lungu(a)iam.unibe.ch>wrote;wrote:
Hi guys!
We've been looking with Alex today at a model built with VerveineJ and
imported in Moose.
In the following example:
public class
<http://grepcode.com/file/repo1.maven.org/maven2/net.sf.jung/jung-graph-impl/2.0.1/edu/uci/ics/jung/graph/OrderedKAryTree.java#>
OrderedKAryTree<V, E> extends
AbstractTypedGraph<http://grepcode.com/file/repo1.maven.org/maven2/net.s…
<V, E> implements
Tree<http://grepcode.com/file/repo1.maven.org/maven2/net.sf.jung/jung-ap…
<V, E>
If I obtain the object referring to the OrderedKAryTree and I call
superclass I get Tree instead of AbstractTypedGraph.
However, if I call directSuperclasses I get both Tree and
AbstractTypedGraph.
Is this normal behavior?
Thanks,
M.
* Code available at:
http://grepcode.com/file/repo1.maven.org/maven2/net.sf.jung/jung-graph-impl…
--
Mircea Lungu, PhD.
Researcher
Software Composition Group
University of Bern
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev