[slimpl] How to help Slimpl

[Dmitry Petukhov]

2006/2/24, Larry Clapp <larry at theclapp.org>:
>
>
> In another thread, also about the event issue, I said we could just
> use all synchronous calls for the moment, and someone objected
> (paraphrasing from memory), "What about when the debugger pops up?"  I
> don't think that that, in and of itself, presents a problem.  In
> general, you send an expression to Lisp, and it either sends back a
> result or sends back a debug sequence.  It doesn't just "pop up", as
> near as I can tell.


I said about 'debugger pops up'. It actually pops up when you write
UncommonWeb app, and an error occurs while you interacting with your web
application.


> The whole asynchronous calls thing only really comes up if you have an
> expression that takes a long time to run, or "never returns", like if
> you start a web server and only want it to come back if it raises an
> error.  Maybe I can create a "pseudo-synchronous" call, where I wait
> for a second for the result, and then transform it to an asynchronous
> call.  Or something like that.


When we can do async call, why even use synchronous ? But unfortunately, we
don't have a decent mechanism for async call. I'm thinking of a separate
process what sits between slime and slimpl and alert slimpl on events. I'll
try to get a time to actually implement this, then we will see how practical
it is. Need to dig more into slime code first, because i don't see where the
rest of input data is discarded when large slime request is aborted in the
middle.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.lispniks.com/pipermail/slimpl/attachments/20060224/b4bbe6a9/attachment.html