Denys Duchier wrote:
>The obvious: let the producer send a special value indicating the end
>that can be recognized by the consumer.
>
>
Oh well. It just looked soo cool to write {Map Stream Consumer}...
One more reason to switch to "for" loops: break!
Note1:Seeing that these 2 threads run strictly the same number of times,
I realised they really belong in the same space. Is there any
significant difference between using a regular "script" proc to
bootstrap the root node of a search from the inside as opposed to
"filling it up" from the outside with many Space.inject -s?
(and the input data could go out of scope before the search starts, too!)
Note2:Speaking of loops, I'm trying to teach Oz to Java programmers
here, they love the familiar constructs like functions and "for". They
would love cells, too, if ony its usage syntax were shorter. They say
it's multiparadigm all right, but it's not fair they have to type so
much more than other paradigm people. Declaring a variable "final" is
just 1 extra word in Java, in contrast.
Gabor Szokoli
-
Please send submissions to users@mozart-oz.org
and administriva mail to users-request@mozart-oz.org.
The Mozart Oz web site is at http://www.mozart-oz.org/.
Please send bug reports to bugs@mozart-oz.org.