Chris,
Let's create this future:
[ 1 sleep "hey" ] future
Then dup it and wait for it:
dup ?future .
After a while I "hey" is printed. I still have the original future on the
stack. If I call '?future' on it again, it actually blocks. Is this the
correct behaviour?
Ed
-
It's a bug. It should do what promises do, and return the future value.
On Feb 6, 2008 9:56 PM, Eduardo Cavazos <[EMAIL PROTECTED]> wrote:
> Chris,
>
> Let's create this future:
>
> [ 1 sleep "hey" ] future
>
> Then dup it and wait for it:
>
> dup ?future .
>
> After a while I "hey" is pr
Chris Double wrote:
> It's a bug. It should do what promises do, and return the future value.
I'll fix it.
Slava
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk
