> Oh, actually, this made me think of something I wanted to bring up. What > we're talking about now is basically a config file, but we already have > something called that. I was describing M5 to some folks at work a little > while ago, and there seemed to be some confusion about how configuration > worked. I think they may have assumed ahead of time a config would be more > like a static file of values (like the ini-s used to be). > > So to straighten out both of those issues, what if we called these default > and command line values the configuration, and then call the python scripts > simulation scripts? That disambiguates the term and hopefully makes it more > obvious what, say, se.py is for and how to set up a simulation. I think it's > something people usually figure out relatively quickly, but it wouldn't hurt > to make it a little more obvious.
Makes sense, but would probably require renaming the directory. _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
