Sun Apr 24 16:21:59 EDT 2016
Building a malloc-less, static Erlang
Essentially, hardware. The idea being that designing real-time
applications is best done as state machines, not as tasks. Leave the
hardware/software separation to a configuration stage: implement tasks
that handle high event rates in hardware, implement tasks that change
infrequently or don't need fast response times in software.
Processes are static: call tree is known at compile time.
Processes have infinite life span.
Language is immutable, implemented through mutation.
Is it possible, by static analysis of message passing, to restrict the
size of the message queues?