Sort-of reminds me of Concurrent-C, except it doesn’t appear to directly associate data with a task, and it doesn’t appear to allow waiting on multiple events at a time (but also the runtime does more work).------------------------
Nate Fries
nvm: no watching a later video. Basically Concurrent-C with a different syntax.------------------------
Nate Fries
Hello Nathaniel,
- You can wait on multiple events with a “par/or”:
par/or do
await A;
with
await B;
end
or use the sugar:
await A or B;
Lines of execution are very cheap in C?u.
We have applications with tens of them that use around 1K of RAM and 10K of
ROM (on a 16-bit platform).
-
The 3rd and 4th videos show how data can be associated with a task
(sorry, the videos are a bit long). -
About Concurrent-C, AFAIR, it follows a rendez-vouz asynchronous style
(non-deterministic w/ a very different semantics).
C?u is actually based on Esterel (a language from the 80’), with many
differences enumerated in the previous e-mail.–
Francisco
On Sun, May 12, 2013 at 5:18 PM, Nathaniel J Fries wrote:
**
Sort-of reminds me of Concurrent-C, except it doesn’t appear to directly
associate data with a task, and it doesn’t appear to allow waiting on
multiple events at a time (but also the runtime does more work).
Nate Fries
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
Yes, execution order was non-deterministic with Concurrent-C.
the await e1 or e2 syntax is very nice.------------------------
Nate Fries