|
From: Andy C. <ac...@ll...> - 2003-02-13 23:25:13
|
So, what would happen if one scheduled an action for the same time that the action currently being executed is scheduled for? Whatever the answer, is it an intended or unintended result? My guess from look at ScheduleBase is that there would be a problem... but *perhaps* what would happen is that ScheduleBase would first come into the current tick, collect up all of the actions at the current tick, loop over them, and if in the course of looping over those actions new actions were added for that same tick, when the scheduler got to the end of the first group of actions, it would then just see the same "tick" as the tick at the top of the priority queue and repeat the same loop. I realize there are valid questions about whether one should even be *allowed* to do this, but in the meantime, I'm just wondering what the designers think should happen with a tiny bit of explanation... Best, Andy ============================================ Andrew J. Cleary, Software Engineer/Computational Scientist Lawrence Livermore National Labs, 925-424-5890. ============================================ |