Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!decwrl!shelby!neon!Kermit.Stanford.EDU!philip From: philip@Kermit.Stanford.EDU (Philip Machanick) Newsgroups: comp.sys.mac.programmer Subject: Re: THINK C problems followup, suggestions Message-ID: <1990Mar4.194322.27068@Neon.Stanford.EDU> Date: 4 Mar 90 19:43:22 GMT References: <390@fornax.UUCP> Sender: root@Neon.Stanford.EDU (System PRIVILEGED Account) Reply-To: philip@pescadero.stanford.edu Distribution: na Organization: Computer Science Department, Stanford University Lines: 35 In article <390@fornax.UUCP>, mcdonald@fornax.UUCP (Ken Mcdonald) writes: > A little while ago, I sent out a message concerning problems I was having > with THINK C 4.0--it wouldn't print properly, and it caused system > crashes after quitting the program. This is the followup to that, along > with some suggestions--and kudos! > [lots deleted] > > 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. > > Hope the above has been of some use. To someone. Somewhere. > > Ken McDonald > {mcdonald@cs.sfu.ca} THINK Pascal allows you to save settings. Breakpoints can be saved with the source, if you save as THINK Pascal, instead of plain text. The Instant and Observe windows can be individually saved; in fact, you can save more than one of each for a given project, which means you can keep a bunch of different debugging contexts, and open them as needed. Why doesn't the same manufacturer do all this for its C environment? Is this a case of a left and right hand that don't talk to each other? I can see the attraction of specializing an environment to a language (not to mention keeping the impementation teams small and manageable), but wouldn't it be great if THINK C and Pascal were available out of one environment? Philip Machanick philip@pescadero.stanford.edu