Subject: Re: Debugging mispellings?
From: Erik Naggum <>
Date: 1997/10/14
Newsgroups: comp.lang.lisp
Message-ID: <>

* Rainer Joswig
| Hmm, Common Lisp code with Macros or Macros generating Macros is
| notoriously difficult to debug.  Often you don't have an idea what
| generated your code or what your current stack frame corresponds to.
| Without a good idea about Common Lisp and the application it is
| completely unthinkable to debug some of the advanced programs.  There is
| no real chance for source line debugging.

I would have thought that an (optimize (debug 3)) declaration in effect
would have made such information available even in a compile-only Common
Lisp, but I think I prefer having an interpreter available when debugging,
although there is still a problem when running macro expansion functions.
`step' is source line debugging for me.

the only time I have missed source line debugging is when finding the rare
compiler bug, not when finding my own bugs.

if you think this year is "97", _you_ are not "year 2000 compliant".

see for Emacs-20-related material.