[slime-devel] Re: Slime?
Luke Gorrie
luke at bluetail.com
Thu Jun 10 04:45:24 UTC 2004
Hi Mike,
Sorry about the wait, I put the mail aside while CVS was down. I'm
CC'ing the mailing list now that it's back.
"Mike Beedle" <beedlem at e-architects.com> writes:
> Luke:
>
> Some quick feedback. Overall, SLIME is great.
>
> I like it much better over ILISP or ELI.
>
> Here are some comments, mostly on the debugger. (You
> may already know some of these things.)
>
> 1. LINUX
>
> CMU 18e (Linux)
> ---------------
> (loaded as inferior lisp)
>
> 1. s, sldb-step does not work AND causes the connection to
> be dropped
I've disabled the step command in the Elisp end. It doesn't seem to be
implemented by any backend, nor have an interface definition. (Anyone
know the history?)
> 2. v works on "swank" frames but it does not work for
> the compiled code.
This works for me. Can you post more details, e.g. a step by step
example?
The Swank frames aren't treated specially so possibly there is
something funky about the other frames your v'ing.
> l, d, i, t, r, etc. all work.
>
> Allegro 6.2 (Linux)
> -------------------
> (loaded as inferior lisp)
>
> 1. s, sldb-step does not work AND causes the connection to
> be dropped:
>
> [Symbol "SLDB-STEP" not found in the SWANK package.
> [file position = 28]]
(As above.)
> 2. v does not work
This feature isn't implemented in the ACL backend.
> 3. l sort of hangs the process but Ctrl-g get it out of the
> state.
I don't have ACL installed to test this. Anyone?
> 2. XP
>
> Clisp 2.33.1 (XP)
> -----------------
> (loaded as inferior lisp)
>
> 1. s, sldb-step does not work but there are no sides effects
> (as far as I can tell).
(As above.)
> 2. v, for jumping to the code on the debugger does not work
The command isn't implemented in the CLISP backend.
> Allegro 6.2 (XP)
> ----------------
> (loaded through swank interface through ACL.)
>
> 1. s, sldb-step does not work AND causes the connection to
> be dropped:
>
> [Symbol "SLDB-STEP" not found in the SWANK package.
> [file position = 28]]
>
> 2. v, for jumping to the code on the debugger does not work
These are as above.
The last ones sound nasty:
> 3. l on the debugger causes both Emacs and Allegro to hang,
> but you can get out with Ctrl-g on Emacs and by
> hitting RETRUN on Allegro (I think).
> 4. Esc (Meta) - . does not work
> 5. Get a "broken Allegro process" on exit from Emacs:
>
> ;; [eof encountered on stream
> #<MULTIVALENT stream socket connected from localhost/4005 to
> localhost/3809 @ #x206738f2>]
Anyone able to investigate?
I'm not wild about ACL's licensing mechanism and would prefer not to
install it on my computer.
Cheers,
Luke
More information about the slime-devel
mailing list