Hi,
In C/C++ you can define something like this: typedef Type TypeAlias; To be able to model this in FAMIX, I introduced FAMIXTypeAlias in Famix-C. However, now I think we have to move it to the Core because of the following reason. Suppose we have something like this: typedef Type TypeAlias; SubType: TypeAlias When enumerating the subclasses of Type, I need to get: - TypeAlias - SubType To do this, when traversing with subclassesDo: I need to take into account the typeAliases associated with each type. This means that the notion of TypeAliases must be in the Core. I hope I explained the matter. Please let me know if you see other alternatives. Cheers, Doru -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Looks reasonable and cheap.
I will work on the canalyzer in a couple of weeks. Alexandre On 9 Sep 2011, at 10:55, Tudor Girba wrote: > Hi, > > In C/C++ you can define something like this: > typedef Type TypeAlias; > > To be able to model this in FAMIX, I introduced FAMIXTypeAlias in Famix-C. However, now I think we have to move it to the Core because of the following reason. > > Suppose we have something like this: > typedef Type TypeAlias; > SubType: TypeAlias > > When enumerating the subclasses of Type, I need to get: > - TypeAlias > - SubType > > To do this, when traversing with subclassesDo: I need to take into account the typeAliases associated with each type. This means that the notion of TypeAliases must be in the Core. > > I hope I explained the matter. Please let me know if you see other alternatives. > > Cheers, > Doru > > > > -- > www.tudorgirba.com > > "To lead is not to demand things, it is to make them happen." > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Tudor Girba-2
On Sep 9, 2011, at 3:55 PM, Tudor Girba wrote: > Hi, > > In C/C++ you can define something like this: > typedef Type TypeAlias; > > To be able to model this in FAMIX, I introduced FAMIXTypeAlias in Famix-C. However, now I think we have to move it to the Core because of the following reason. > > Suppose we have something like this: > typedef Type TypeAlias; > SubType: TypeAlias > > When enumerating the subclasses of Type, I need to get: > - TypeAlias > - SubType > > To do this, when traversing with subclassesDo: I need to take into account the typeAliases associated with each type. This means that the notion of TypeAliases must be in the Core. doru we are about to generate a doc for famix 30, it would be nice that this kind of discussions get written in the class comment/description so that we do not lose it. > > I hope I explained the matter. Please let me know if you see other alternatives. > > Cheers, > Doru > > > > -- > www.tudorgirba.com > > "To lead is not to demand things, it is to make them happen." > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |