Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!rutgers!usc!jarthur!wilkins
From: wilkins@jarthur.Claremont.EDU (Mark Wilkins)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C problems followup, suggestions
Message-ID: <4805@jarthur.Claremont.EDU>
Date: 4 Mar 90 13:03:14 GMT
References: <390@fornax.UUCP>
Distribution: na
Organization: Harvey Mudd College, Claremont, CA 91711
Lines: 19

In article <390@fornax.UUCP> mcdonald@fornax.UUCP (Ken Mcdonald) writes:
>I find myself running debugging sessions which are very similar
>to one another, in that I want to look at the same variables, set the
>same breakpoints, etc.  It would be nice if there were a way for the
>debugger to remember these settings.  It would be even nicer if, right
>in the source code, a programmer could specify where breakpoints should
>be set, which expressions should appear in the data window, etc.


   YES, yes yes yes YES yes yes YES !!!!!!

  There is nothing more frustrating than debugging a TCL program, and being
able to visualize EXACTLY where in the code you want to go WITH NO MEANS TO
GET THERE!  Even if there were an "Open file..." option somewhere in the
debugger so that a given source file could be opened that would be a BIG
improvement!!

-- Mark Wilkins
   wilkins@jarthur.claremont.edu