Most of the Erlang-in-Lisp issues discussed here and on the mailing list this summer have been rolled into the user manual in some form. Get it here in pdf format or here in HTML.
read the whole post »Tag: erlang-in-lisp
-
-
links, timeouts, and refactoring
First off, I have added some support for timeouts in receive blocks (in erlang this is done with the ‘after’ block). For now this is only supported on the unix-process implementation, but should be easy to implement. While I know that the timeouts are ‘soft’ I do wonder how they ...
read the whole post » -
midterm report
midterm report for the erlang-in-lisp google summer of code project.
read the whole post » -
serializing continuations
Some people in the weblocks community have been thinking about some of the things I’ve been pondering. No real answers. I need to play with the continuations in arnesi and cl-cont, but if we can’t move them between address spaces (either distributed or in different unix processes) it ...
read the whole post » -
matching Erlang’s receive semantics
On Sunday and Monday I patched our version of receive. It now matches the Erlang semantics of blocking until a suitable match is found. This works in the unix-process and thread based concurrency models (it required changes to the API, but shows how we should grow the pluggable concurrency API ...
read the whole post » -
the great CLOS experiment
I just committed the last touches on some pretty major changes in the erlang-in-lisp epmd branch. I was distracted from my linking/registering work on Tuesday by the fragility of the original design. I had an idea to use CLOS and hoped this would help achieve our goals of pluggable ...
read the whole post » -
sname, name, self, node
One of the things I’ve always been unclear on is how a server binds to particular address. This became apparent today in my erlang-in-lisp work with iolib and erlang itself. I had been messing around with distributing the ping-pong example last week and things were not going as smoothly ...
read the whole post » -
ping-pong
The ping-pong example is working with one caveat. Matches against patterns with just one atom must still be wrapped in a list. This is annoying, but we can fix it.
This first step happened a bit more slowly than I’d like, but I can see where we’re going ...
read the whole post » -
eil: top-level
One of the things we may want to think about for erlang-in-lisp is a top level. In erlang, one can send and receive messages right at the REPL because it is a process with a mailbox. For us, we have to do some additional bookkeeping (thus the standard REPL is ...
read the whole post » -
simple example working
I have a very simple example (sort of) working in erlang-in-lisp/examples.lisp. I did a quick hack to integrate fare-match into send/receive. The matching really isn’t working because the message is being mangled before it is sent over the socket. More tomorrow…
read the whole post »
Page 1 / 2 »