sub doMyThing() {
   doStuff;
   waitFor( condition);
   doMoreStuff;
}
[download]

We can provide a function to the users that hides some "magic" in there that we may be able to use to provide this functionality, but I'm unsure the best way to do this.

I have given this some thought, we would like to make the interface to the users as simple as possible while leaving as much power in the users hands.

One way to make the users use some sort of wrapper functions, which we would like to avoid if possible, so we can later skip back to the waiting:

sub doMyThing() {
   waitWrapper( condition) {
      doStuff;
   } waitFor( condition);
   doMoreStuff;
}
[download]

Then we use some sort of variables to determine which waits we have hit and where we can jump back to after the restore().

Edit: I was informed that save() restore() is not a common concept.
In running our simulations we need the ability to simulate to a point and save the state of the run. This includes all variables and state. Then later we can jump to that point without spending the time computing the state.
This saves us hours of time when debugging a problem and is an essential tool for us.
EndEdit