> To get back to this original problem (which I just ran into myself, > making me pay more attention to this thread...): do we really need a > separate enums package? It seems pretty unlikely you'll ever want the > enums without the params, and while you might be able to use some > params without the enums it'd be handy to get them both for free. > > Also, assuming we want "external" scripts to use these enum values, it > might not be appropriate to have them in a package that starts with > "internal". > > I see that objects/__init__.py does a "from m5.internal import > params", so object.params still works; if we just change > internal/params.py to import all the modules that start with either > param_ or enum_ and get rid of the enum package, then simulate.py (and > presumably anywhere else we might use objects.params.<enum-value>) > doesn't have to change. No, it's not necessary. It's just how I ended up doing it. I think this last proposal is the right one. It would probably be a few days before I can get to it, but it should be trivial enough for you if you were willing to do it and test it.
Nate _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
