5:40:55beachShinmera: So what made you create Dissect when I suppose SWANK already existed?
6:19:15ShinmeraSwank'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:41beachHere 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:52ShinmeraSounds good. My initial use-case for Dissect was for non-interactive debuggers (loggers, web displays, etc.) so it should have most things.
6:25:04beachI see. Though scymtym indicated a few things that could be handy in an interactive debugger.
6:25:16ShinmeraYeah, eval-in-frame being the big one.
10:18:34Shinmerabeach: mostly the documentation, which was very rushed
10:18:49Shinmerafor the rest it isn't present enough in my mind to know what would need doing.
10:23:47ShinmeraThe API's been out there for a long time and there are people depending on it, so I would be reluctant to change the public-facing stuff without compatibility