> So I guess the upshot is that if there are complex Ruby types (not > just typedefs of builtin types) that want to have standard ways of > printing themselves out, that's kind of inconsistent with M5 right > there :-), but if you want to keep that behavior then overloading > operator<< is the way to do it.
Gabe is adding a PC type though and I believe he's overloading operator<<. I generally think that this is a pretty nice thing to do. It's more or less analagous to implementing __str__ in python which is a pretty nice thing to have, so I'd say that Ruby is pushing a good idea into M5. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
