[no subject]

I can see use cases such as:

I want to contact X buyers and Y sellers in parallel. I decide whom and
how many at runtime. I construct the arguments for each buyer and each
seller and collect them in an iterator.

The <prototype> is a directive. A new instance of whatever is within the
prototype is created.
For simplicity let us assume only scopes are allowed. <prototype> takes
an attribute, iterator.
The iterator is used to initialise activities within the prototype.


<flow>
   <prototype argumentList=3D"buyerArgumentsIterator">
      <scope>
   </protype>

   <prototype argumentList=3D"sellerArgumentsIterator"
     <scope>
   </prototype>
</flow>

In the absense of a parameterized activity, we can pretend that <flow>,
using arguments from the iterator, is initializing local variables in a
specific scope.
In turn the iterator item, argument, is a name/RHS pair.

This does what Yaron's 147 does with some differences.
First a new construct is not added. Secondly I can use many different
iterators within the same concurrency construct without adding difficult
control logic. I also suspect this construct is more readable.

I know this is just a sketch of a solution.....

Cheers,
Andrew