tag:blogger.com,1999:blog-2080885971644496896.post2650374273353885414..comments2009-12-20T17:24:18.361-05:00Jens Axel Søgaardhttp://www.blogger.com/profile/15211030864341077735noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-2080885971644496896.post-14608777331419680172009-12-20T17:24:18.361-05:002009-12-20T17:24:18.361-05:00Well, parallelism is an important difference, of course (enough that warrants its own, separate api so programmers know what they are getting), but another difference is that with promises the computation won&#39;t get &quot;frozen&quot; in the way that futures can get frozen.Robbyhttp://www.blogger.com/profile/08402308775580442837noreply@blogger.comtag:blogger.com,1999:blog-2080885971644496896.post-86446418262008632142009-12-20T07:11:12.798-05:002009-12-20T07:11:12.798-05:00It seems to me that delay/thread in scheme/promise has an analogous existing interface to a later forced-touched promise-future. Outside the very important and appreciated implementation difference of having multiple CPUs, where does the analogy fall short enough to require a different set of functions?griffinishhttp://www.blogger.com/profile/16994898111283078052noreply@blogger.comtag:blogger.com,1999:blog-2080885971644496896.post-22414492506137858732009-12-07T18:39:21.913-05:002009-12-07T18:39:21.913-05:00No. You can have as many versions as you want, completely separate. (Double clicking in the finder will always choose one of the open drschemes; I haven&#39;t figured out what the OS does when none of them are open.)Robbyhttp://www.blogger.com/profile/08402308775580442837noreply@blogger.comtag:blogger.com,1999:blog-2080885971644496896.post-15698133566916469352009-12-07T18:31:17.086-05:002009-12-07T18:31:17.086-05:00Does that &quot;mess up&quot; anything with the packaged installation?Roberthttp://www.blogger.com/profile/05513580456463140264noreply@blogger.comtag:blogger.com,1999:blog-2080885971644496896.post-8704160124165621342009-12-07T18:05:59.366-05:002009-12-07T18:05:59.366-05:00Eventually, yes. But it is easy to build under mac os x. Just make sure you have the developer tool installed and then it is only a few simple commands in a Terminal window.Robbyhttp://www.blogger.com/profile/08402308775580442837noreply@blogger.comtag:blogger.com,1999:blog-2080885971644496896.post-47902005230048363832009-12-07T18:01:46.555-05:002009-12-07T18:01:46.555-05:00Will never versions have it enabled by default for the OSX package?Roberthttp://www.blogger.com/profile/05513580456463140264noreply@blogger.comtag:blogger.com,1999:blog-2080885971644496896.post-8704605877696933962009-12-07T14:20:25.568-05:002009-12-07T14:20:25.568-05:00One could build another layer on top of this one to do things like that (and perhaps we should not have taken over the names &#39;future&#39; and &#39;touch&#39; and let a library like that have them).<br /><br />touch is explicit so that the runtime system primitives that depend on a particular context are well-defined (eg, exception handlers and continuation marks).Robbyhttp://www.blogger.com/profile/08402308775580442837noreply@blogger.comtag:blogger.com,1999:blog-2080885971644496896.post-66963695086332782222009-12-07T14:18:18.960-05:002009-12-07T14:18:18.960-05:00Why is the touch explicit? <br /><br />Why don&#39;t you use future-strict primitives to force future values?matthiashttp://www.blogger.com/profile/00000181081270224360noreply@blogger.com