Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!rutgers!mephisto!ncsuvx!news
From: dks@shumv1.uucp (D. K. Smith)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C problems followup, suggestions
Message-ID: <1990Mar4.194258.22693@ncsuvx.ncsu.edu>
Date: 4 Mar 90 19:42:58 GMT
References: <390@fornax.UUCP>
Sender: news@ncsuvx.ncsu.edu (USENET News System)
Reply-To: dks@shumv1.ncsu.edu (D. K. Smith)
Distribution: na
Organization: NCSU Computing Center
Lines: 18

In article <390@fornax.UUCP> mcdonald@fornax.UUCP (Ken Mcdonald) writes:

[deleted bunch of stuff about THINK C 4.0... 
		sounds like Init'itis too me :-) ]
>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.


Place the statement   "Debugger();"    '...right in your source code...'

I think this traps to the same address as the _Debugger in assembly code.

dk smith
------------------------------------------------------------------------
dks@shumv1.ncsu.edu                |                ude.uscn.1vmuhs@skd
-my opinions reflect my opinions.  |  .snoinipo ym tcelfer snoinipo ym-
------------------------------------------------------------------------