Statment reached after persisted Yield

Interleave can only be activated. Interleave is the only arbiter that has no "termination". So yielding to it, does nothing.

Receive, Choice, Join, MultipleReceive etc all are considered "done", when some messages are received, satisfying the constraints. Interleave on the other hand can have persisted handlers that stay alive forever. So it would never end up terminating, blocking your iterator.

Activate() is really a form of "spawn" or "execute in parallel", which is exactly what interleave needs, as a long running arbiter.

GeorgeChrysanthakopoulos at 2007-10-3 >

Hi George,

Your post says:

George Chrysanthakopoulos wrote:

..........Interleave on the other hand can have persisted handlers that stay alive forever. So it would never end up terminating, blocking your iterator.

And the user guide says:

Important: Never yield to persisted receivers within an iterator. In the yield statement above, Arbiter.Receive is called with persist = false (the first argument). If the receiver is persisted, the yield is never considered satisfied, so the iterator will never progress to the next statement after the yield

Well, yesterday I yielded (by mistake) a persisted receiver and the statment after the yield was reached.

Try this:

class Program

static void Main(string[] args)

{

Dispatcher dispatcher = new Dispatcher(0, "Yield Test");

DispatcherQueue dq = new DispatcherQueue("Yield Test Queue");

intPort = new Port<int>();

for (int i = 0; i < 5; i++)

{

intPort.Post(i);

}

Arbiter.Activate(dq,Arbiter.FromIteratorHandler(ErroneusPersistentYield));

Console.ReadLine();

}

private static Port<int> intPort;

private static IEnumerator<ITask> ErroneusPersistentYield()

{

yield return Arbiter.Receive<int>(true,intPort, delegate(int i) {Console.WriteLine(i.ToString());});

Console.WriteLine("After yield reached");

}

My pc output is:

0

1

After yield reached

2

3

4

I debugged and the yield ends when the first task is completed (the persisted reciever continues its work, of course). Yield a persisted receiver is useless, but the iterator progress to the next statment after the yield (at least my computer progress to the next statment).

SERware at 2007-10-3 >

As far as I know, throwing a exception is the best semantic in this case.

Thanks

PD. It was a copypaste accident.

SERware at 2007-10-3 >