ruby: slicc: derive DataMember class from Var instead of PairContainer
Review Request #3084 - Created Sept. 1, 2015 and submitted
| Information | |
|---|---|
| Nilay Vaish | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 11079:d0e52637c510 --------------------------- ruby: slicc: derive DataMember class from Var instead of PairContainer The DataMember class in Type.py was being derived from PairContainer. A separate Var object was also created for the DataMember. This meant some duplication of across the members of these two classes (Var and DataMember). This patch changes DataMember from Var instead. There is no obvious reason to derive from PairContainer which can only hold pairs, something that Var class already supports. The only thing that DataMember has over Var is init_code, which is being retained. This change would later on help in having pointers in DataMembers.
It's too bad none of the code has any comments.