tag:blogger.com,1999:blog-8383004232931899216.post4335454659272943119..comments2023-11-01T11:47:57.046-04:00Comments on Designing ParaSail, a new programming language: Handling concurrent events in ParaSailTucker Tafthttp://www.blogger.com/profile/08866496974237052847noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8383004232931899216.post-28626018224559139942012-11-26T12:23:34.322-05:002012-11-26T12:23:34.322-05:00The "select" construct has been complete...The "select" construct has been completely removed from ParaSail, as of 11/2012. Use the "exit ... with" (or "return") construct instead. Both exit and return now support exiting from parallel contexts, automatically terminating the non-exiting/non-returning threads as appropriate (but first waiting for locked operations to complete).Tucker Tafthttps://www.blogger.com/profile/08866496974237052847noreply@blogger.comtag:blogger.com,1999:blog-8383004232931899216.post-79633723816486666602011-07-07T18:32:43.286-04:002011-07-07T18:32:43.286-04:00The "select" construct does not seem fun...The "select" construct does not seem fundamental, as it can effectively be accomplished using a block with multiple threads, where each thread exits with an indication of which call finished first. That indication can then be used to determine what to do next. In general, the "exit ... with" seems adequately flexible to make the special-purpose "select" unnecessary. <br /><br />Bottom line: we don't mention the "select" construct in the current ParaSail reference manual (available at https://groups.google.com/forum/#!forum/parasail-programming-language).Tucker Tafthttps://www.blogger.com/profile/08866496974237052847noreply@blogger.com