Path: utzoo!attcan!uunet!unisoft!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Wishlist for THINK _C_ (4.1 ? 5.0 ?)
Message-ID: <11101@hoptoad.uucp>
Date: 13 Apr 90 15:21:01 GMT
References: <3192@draken.nada.kth.se> <2274@cbnewsk.ATT.COM> <3200@draken.nada.kth.se> <90083.132800CXT105@psuvm.psu.edu> <2993@murtoa.cs.mu.oz.au> <16903@well.sf.ca.us> <17184@well.sf.ca.us>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 28

In article <16903@well.sf.ca.us> nilesinc@well.UUCP (Avi Rappoport) writes:
>>What I really need is a way to keep my breakpoints and variables between
>>runs of the program.  So annoying to have to keep resetting them.

I've often thought this myself.  Oh, Riiiich.....

In article <17184@well.sf.ca.us> mjf@well.UUCP (Marty Fried) writes:
>I too was frustrated with that aspect of the debugger.  I have just discovered
>that you can use the "skip to here" function to re-run from any point, even 
>from the beginning.  If you select the first statement, then select skip to
>here, the program will start at that point.  I haven't had a chance to fully
>test this out, but it seems to work.

Except that your global data will not get reinitialized, so it's not
the same as re-running the program.  It could very well give misleading
results; in fact, it's almost sure to, if you use any globals and count
on C to initialize them to zero or to what your source code's
initializers specify.  I would recommend not using this strategy except
possibly very early in the running of your program, or if you are using
very little global data and not couting on its initialization.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"Do what you wanna, do what you will;
 Just don't mess up your neighbor's thrill.
 And when you pay the bill, kindly leave a little tip
 To help the next poor sucker on his one-way trip."
    - Frank Zappa, "You Are What You Is"