Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!munnari.oz.au!metro!usage.csd.unsw.oz.au!hydra.maths.unsw.oz.au!jim
From: jim@hydra.maths.unsw.oz.au
Newsgroups: comp.lang.prolog
Subject: better than 4-port debugger
Message-ID: <1793@usage.csd.unsw.oz.au>
Date: 24 Jun 91 01:12:41 GMT
Sender: news@usage.csd.unsw.oz.au
Reply-To: jim@hydra.maths.unsw.oz.au ()
Organization: University of New South Wales
Lines: 17


IMHO, four-port debugging may be fine as an underlying model,
but is bad as a view of that model. recently, i was doing some
partial evaluation work and the strutures i was generating filled
several lines on my 4-port debugger. what i would have prefered
is a debugger ala Smalltalk where the call history is on a
click and point list in a window and clicking on item in that
list pops up another window with all the arguments listed in another
list. clicking on any one argument would print it to a third window.

sound tricky, right? actually, its wonderfully easy to use. the
debugger was one of the main reasons I switched from KEE on a LISP
machine to Smalltalk/V under DOS. I had all the debugging productivity
and none of the LISP machine overheads.

tim menzies.   (timm@spectrum.cs.unsw.oz.au)