> That said, using python to generate python to put in a hidden directory to > read with python embedded in a binary is, in my opinion, WAY more > complicated than the problem warrants. The generating script would have to > be fairly smart too so you could quickly update particular fields, remove > previously set defaults, etc. > > How about a file with key value pairs separated by equals signs. Those would > be used as the defaults when the options were set up, and that would be the > whole deal. If somethings doesn't make sense as an option to the m5 binary, > it wouldn't go in that file.
This is probably right. Though I think the name = value file should either be python code (this is more or less how it is now since you just do name=value and not much else.) or a .ini (because there's an easy to use parser and it's a well known file format). _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
