[Ecls-list] Line Number of errors ?

[Tobias C. Rittweiler]

Hi Juan,

sorry for the late reply. I marked your original mail but never came to
actually answer it.


"Juan Jose Garcia-Ripoll" writes:

> I now have a problem which I ignore whether other implementations
> faced, which is that Slime's functions appear in those backtraces.
> ...

Right. SBCL solves this by having a notion of interrupted frames,
and providing a means to get at the topmost interrupted frame.

In swank-backend:call-with-debugging-environment which is promptly
called in Slime's customized *debugger-hook*, the topmost (i.e. most
recently) interrupted frame is remembered, and when computing a
backtrace, the frame grovelling starts at the remembered place.



> As for the other stuff, which is registering functions and objects
> with the source files in which they appear, what I can do is to
> provide hooks into the standard macros, DEFSTRUCT, DEFCLASS, etc.
>
> My current idea is the following: I will add a form (REGISTER-SOURCE
> object file position). REGISTER-SOURCE will be a macro that will, by
> default, expand to (PROGN) and, in case you redefine it through slime,
> it may give rise to a more complicated registration into a database
> that Slime can use.
>
> I think it is a good compromise. Do you agree?

This sounds fine. Thanks for your work!

  -T.