16. Developing and Debugging
The Lisps that were dominant at the time when COMMON LISP was created, already had impressive interactive debugging facilities, and so the standard codified that every Lisp should have them. Thus, no matter which implementation you’re using (as long as it conforms to the ANSI standard), your Lisp has to have a debugger, a tracer, an inspector, and several other features discussed in this chapter.1 While offering these features is in a way easy due to COMMON LISP’s image-based nature (see Recipe 16-1), many of the currently popular open source Lisps are quite Spartan compared to their forebears and offer only relatively raw text-based versions of the aforementioned tools.
That’s why you want some kind of IDE wrapped ...
Get Common Lisp Recipes: A Problem-Solution Approach now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
