On 7/10/07, skaller <[EMAIL PROTECTED]> wrote: > [...] > Now, with the new parser in place, some more pleasing > syntax might be invented for this. In particular the above > is not very nice because 'promise' remains in scope after > it has been read .. it should evaporate. > > So, we have the primitives to implement better syntax, I just > dont have enough use cases to see what the better syntax should be. > > For some operations Unix filter is possible notation: > > p1 | p2 | p3; > > because the 'pipes' connecting the threads are anonymous.
You essentially want an "orchestration" language. See Orc [1] for a very simple and general orchestration language. > > You can take this even further and make all computation via such > > calls, and concurrency reduces to safe event-loops. See "Robust > > Composition: Towards a Unified Approach to Access Control and > > Concurrency Control" [1]. > > The thesis is rather long, but I've looked at E and am not > particularly convinced. Convinced of what? The concurrency safety? The security claims? E covers quite a bit of ground. Sandro [1] http://www.cs.utexas.edu/users/wcook/projects/orc/ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
