Hi Brad, Steve told me that you were going to work on putting Ruby events into the M5 event queue. It shouldn't be much of a surprise, but I definitely have some opinions on how things should work long term. I'd actually like to add a "clock" to SimObject (or perhaps ClockedObject) where it has an idea of a clock period, and phase, and allows you to schedule events on the event queue based on clock cycles instead of ticks. This basically means clock and phase variables and a scheduleClock() function to the base SimObject type. I'd think that this would make your conversion of RubyEvents considerably easier. I basically have this code done.
Steve mentioned that you were planning on wrapping RubyEvents, so perhaps you're not quite ready to fully convert RubyEvents to M5 Events, but even so, this sort of thing might help. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
