How to write Common Lisp in 2017 – an initiation manual

Re:How to write Common Lisp in 2017 – an initiation manual by ane on Wednesday March 29, 2017 @04:01AM (#13984248)

CIDER has had debugging abilities like this for a year, there's a sexp based interactive debugger that allows injection, evaluation, stepping etc.

Here's a 39 second video about it https://www.youtube.com/watch?v=A3JAlWM8qRM

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by lispm on Wednesday March 29, 2017 @04:11AM (#13984288)

The debugger needs to 'instrument' the code with breakpoints...?

That's something different.

In a Lisp system I would have an arbitrary amount of code and can halt and inspect/debug any code without any prior need to 'instrument' code.

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by ane on Wednesday March 29, 2017 @05:59AM (#13984682)

To debug a function, yes, you need to eval the form using instrumentation. Then the debugger starts when this form is evaluated. This is the the only major difference to what SLIME provides. Adding breakpoints is somewhat easier with cider, you don't need to call break but you can just add a breakpoint to any sexp by pressing b.

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by lispm on Wednesday March 29, 2017 @06:12AM (#13984743)

> Then the debugger starts when this form is evaluated.

You mean the stepper using break-instrumented code? That's just a part of what one would call 'debugger' in Lisp.

What CIDER calls 'debugger' would be mostly called 'stepper' in Lisp.

http://franz.com/products/allegro-common-lisp/stepper_dialog...

http://www.lispworks.com/documentation/lw70/IDE-M/html/ide-m...

> Adding breakpoints is somewhat easier with cider, you don't need to call break but you can just add a breakpoint to any sexp by pressing b.

LispWorks does that, too. Usually via a break icon in the window toolbar or the context menu.

[ Parent | on HN ]