Re: dspec and lisp-unit vs debuggable macros

Thanks for the tip. When I get the time, I'd like to generate as detailed of a Dspec as possible for define-test.

----------------------------------------------------------------
Thomas M. Hermann
Odonata Research LLC
http://www.odonata-research.com/
http://www.linkedin.com/in/thomasmhermann

On Mon, Mar 4, 2013 at 12:02 PM, Denis Budyak <budden73@gmail.com> wrote:

Thomas, in your case something like

(dspec:define-dspec-alias define-test (x) `(defun ,x))

might help.

Dspec machinery gives only a coarse control, it allows to find top-level form
only, AFAIK. This is, definitely, better than nothing.

"Debugger Edit" command uses additional (undocumented) machinery to find exact
location of a error inside of toplevel form.

> I see that my response didn't really address the issue that you were raising.
Now that I understand it, this is actually a problem with define-test in
lisp-unit. It is not possible to go to source when there is an error in an
assertion. While annoying, I've had bigger issues to address and have just let
this slide.
>
>
> Isn't this problem addressed in LispWorks by Dspecs: Tools for Handling
Definitions?
>