Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!mips!apple!well!oster
From: oster@well.sf.ca.us (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Wishlist for THINK _C_ (4.1 ? 5.0 ?)
Message-ID: <17216@well.sf.ca.us>
Date: 13 Apr 90 14:59:47 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: oster@well.UUCP (David Phillip Oster)
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 28

In article <17184@well.sf.ca.us> mjf@well.UUCP (Marty Fried) writes:
_>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 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 have also used the console routines to resize and even rename to console
_>window.  (using stdin and stdout as the FILE *).  I had to edit console.c to
_>make it work, though.

Unfortunately, if you write real Mac applications, which you apparently do not
since you care about console i/o, you'll find that starting from the first
statement is not the same as the initial start up in critical ways:

1.) You will be calling the ToolBox initialization routines in an
environment where thay have already been called.

2.) any memory allocation routines you call will  allocate new storage
without ever freeing the old stuff from the previous run. (GetMenu, for
example.)

It is a nifty hack when it works, but don't expect it to work too well.
-- 
-- David Phillip Oster - Note new address. Old one has gone Bye Bye.
-- oster@well.sf.ca.us = {backbone}!well!oster