`system debugging' environments
Tim Bradshaw
This is sort-of a followup to the interminable `is there a debugger or
similar ...' thread, but it's actually a real question asked because I
actually want to learn something.
When I'm writing things, I very often get to the point where I want to
be able to `debug' things. What I mean by `debug' not the traditional
thing, but something like `draw a picture of this datastructure so I
can work out why my program that walks over it is not working' or
`draw a histogram of this vector so I can see how well my hashing
function is doing', or any other of a number of
data-visualisation-type things.
The best environment I've *found* for doing this is my symbolics, but
it's not that realistic to use that all the time. But it's crucial
that doing this is cheap in programming time, because otherwise I
won't do it. I don't really care if the resulting thing is a bit slow
-- I typically only run is 5 times.
Does anyone know which of the current Lisps best supports this sort of
cheap once-off data-visualisation? Can CLIM do it without being
ludicrously OTT (I don't really want to do this whole
define-application thing just to see a histogram)?
Thanks
--tim
Rainer Joswig
In article <ey3zpml...@eigg.aiai.ed.ac.uk>, Tim Bradshaw
<t...@aiai.ed.ac.uk> wrote:
Wasn't CLIP&CLASP supposed to offer a substrate to collect and
visualize program statistics?