Notices

1. blake shaw (rml@functional.cafe)'s status on Saturday, 22-Apr-2023 00:48:13 CEST blake shaw

   What are some ideal bugs for teaching lisp debugging?

   • screwtape (screwtape@mastodon.sdf.org)'s status on Saturday, 22-Apr-2023 00:48:13 CEST screwtape

     in reply to

     • LdBeth
     • svetlyak40wt
     • Nicolas Martyanoff

     @rml which lisp? @svetlyak40wt @galdor @ldbeth honestly I don't use common lisp's lldb or even 'inspect much so I second this question. What are some good things to start fixing?

   • blake shaw (rml@functional.cafe)'s status on Saturday, 22-Apr-2023 00:48:13 CEST blake shaw

     in reply to

     • screwtape
     • LdBeth
     • svetlyak40wt
     • Nicolas Martyanoff

     @screwtape @ldbeth @galdor @svetlyak40wt was thinking sticking to lisp(s) in general might generate some likewise-applicable responses, but wanted to limit it to #lisp so that things don't stray too far off into the well-trodden #gdb debugging discourse

   • screwtape (screwtape@mastodon.sdf.org)'s status on Saturday, 22-Apr-2023 00:48:25 CEST screwtape

     in reply to

     • LdBeth
     • svetlyak40wt
     • Nicolas Martyanoff

     @rml @ldbeth @galdor @svetlyak40wt Maybe try invoking common lisp's 'INSPECT to enter inspection mode? A simple (or complicated) device is to use 'MACROLET to exploratorily locally clobber erstwhile function calls. I think scheme works too differently to common lisp for debugging to be the same. I'm not going to try to talk about lldb.