> On the face of it, it doesn't sound that bad, but how often does this > really occur? If you have a SimObject that regularly has multiple > events scheduled at the same tick & priority, and is smart enough to > keep track of when that happens, why not have that SimObject chain its > own events itself (i.e., it just schedules one event on the event > queue but that event has the capability of having additional events > tacked on to it).
That's what I've been doing and it's annoying. It's a lot more work. There's just more code that must be written. I wrote a class that did exactly that for me and then I thought, why bother? It's also lower performance because you'll have two virtual function calls (unless the second is not virtual). Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
