Can't we just resolve whatever the conflicts are? Or we could go back to having a ruby_se.py, but have it be a link to se.py, and use sys.argv[0] to decide whether to look for the ruby args? (Not pretty, but sort of backwards compatible without duplicating code.)
I don't fully understand the problem, which can actually be somewhat liberating when it comes to proposing solutions :-). Steve _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
