libera/#commonlisp - IRC Chatlog
Search
18:33:44
scymtym
beach: if you are asking whether the McCLIM debugger currently uses swank, the answer is yes. regarding the question whether it should use swank or dissect, i'm not sure. one thing to keep in mind is that swank provides things other than analyzing the stack: utilities for conditions, functions for working with restarts and eval in frame
18:34:08
scymtym
swank provides return from frame and restart frame as well but i don't think the McCLIM debugger uses those at the moment
19:20:26
jackdaniel
perhaps people work on their own personal dissects because they don't want to spend time on other people projects ,)
23:02:07
copec
I've been setting up dnsdist loadbalancers at my work, it is mostly written in C++ but with LUA JIT bindings, and the config for it is a LUA source file that ends up creating the live running image, which you can alter in most ways in the live server - add/remove backend servers or front end services or routing mechanisms or blocks.
6:19:15
Shinmera
Swank's interface isn't exported or properly documented, and I didn't want to rely on Swank as a library since it has a whole bunch of other stuff, too.
6:21:41
beach
Here is what I think then. I think we (not sure who "we" are yet) should improve Dissect so that it can handle all the stuff we need for a "debugger", and then change or replace the CLIM debugger to use it.
6:23:52
Shinmera
Sounds good. My initial use-case for Dissect was for non-interactive debuggers (loggers, web displays, etc.) so it should have most things.
6:25:04
beach
I see. Though scymtym indicated a few things that could be handy in an interactive debugger.
6:26:46
Shinmera
Mostly because I don't know what Swank provides there or what would even be needed that isn't in the standard already