I recently discovered that the old capability to have a python-only
SimObject to serve solely as a configuration hierarchy node (basically
a SimObject container/cluster/collection/subtree without any C++
counterpart or runtime functionality) went away at some point with
Nate's restructuring. Nate
+class SimObjectCollection(SimObject):
+ type = 'SimObjectCollection'
SimObjectCollection Seems like a pretty long name. Is there something
ambiguous about calling it Collection or Container?
Nate
___
m5-dev mailing list
m5-dev@m5sim.org
On Fri, Mar 27, 2009 at 2:12 PM, nathan binkert n...@binkert.org wrote:
+class SimObjectCollection(SimObject):
+ type = 'SimObjectCollection'
SimObjectCollection Seems like a pretty long name. Is there something
ambiguous about calling it Collection or Container?
Yea, it seems to me that
