[erlang-in-lisp-devel] latest erlang-in-lisp

[Faré]

> This morning I had some troubles again (I forget what it was) and
> updated my copy...right this second I can't actually do a
> slime-load-system without sbcl going bonkers and chewing up 100% of
> the cpu time.  It ties up emacs and I can't even get to *slime-events*
> to see what's going wrong.  I should probably just back off my copy of
> slime.
Sounds like some SBCL problem, combined with some SLIME issue. Maybe
downgrade to some known-working versions?

> In other news, I'm almost done ditching the read/print message
> serialization in favor of cl-store.  I think this will work well, but
> I do not know about performance.

Can you make the serialization method parametrizable?

Or even punt on it for now, considering we're in "pencils down" period.

At this point, it will become more important to ensure there's enough
docs of what's there and what remains to be done for other people to
take over your code.

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Opportunity is missed by most people because it comes dressed in overalls
and looks like work.    -- T. A. Edison