Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!wuarchive!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C problems followup, suggestions
Message-ID: <2052@husc6.harvard.edu>
Date: 4 Mar 90 22:01:39 GMT
References: <390@fornax.UUCP> <4805@jarthur.Claremont.EDU>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Distribution: na
Organization: Symantec Language Products Group
Lines: 28

In article <4805@jarthur.Claremont.EDU> wilkins@jarthur.Claremont.EDU (Mark Wilkins) writes:
>
>  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!!

	If the debugger is running, you can open a file in the environment,
and choose "Debug" from the Source menu; this will open the file in the 
debugger. The file will be scrolled to the selection range in the requested
file.

	User's manual, Chapter 11, page 141 ("Viewing other files in the
source window."); version 4.0.

R.
~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

"When someone who makes four hundred and fifty dollars an hour wants to
tell you something for free, it's a good idea to listen."

~~~~~~~~~~~~~~~