Re: futures in common lisp

If I understand futures right, then they would
need some low-level support from the
Implementation. When the future has computed
a value, then it would need to replaced by
the value. Also problematic: the interaction
with catch/throw and generally the condition
handling. I don't think that's easy to
do "right". Then there is the interaction
with other constructs. + needs its arguments
to compute the sum. CONS could store the
future in a cons and have it replaced
later. Also not easy to provide.

Fully agree to that, I will have a look at QLisp ...

So, from reading about it Futures don't
look that attractive to me - from
an implementation point of view.

From a language point of view it would be more than nice to have, though.

(wow, answering at some beach at the Elbe
with an iPhone :-) )

Reading it close to the Rhine, yet having no iPhone :( but working on this ...

-- Mario
.

Relevant Pages