Path: utzoo!attcan!uunet!ginosko!uakari.primate.wisc.edu!dogie.macc.wisc.edu!gatech!ncar!asuvax!mcdphx!mcdchg!att!cbnewsc!fjo From: fjo@cbnewsc.ATT.COM (frank.j.owen) Newsgroups: comp.sys.mac.programmer Subject: Re: Problem with LSC 4.0 debugger. Message-ID: <3501@cbnewsc.ATT.COM> Date: 27 Sep 89 14:55:54 GMT References: <256@dbase.UUCP> Distribution: na Organization: AT&T Bell Laboratories Lines: 34 From article <256@dbase.UUCP>, by awd@dbase.UUCP (Alastair Dallas): > In article <3425@cbnewsc.ATT.COM>, fjo@cbnewsc.ATT.COM (frank.j.owen) writes: >> I think that the feature described in the original posting is a >> useful and valid one. Other compiler/debuggers (I don't know of any in the Mac >> arena - perhaps the Aztec sdb) have this feature. It IS doable. If >> there are "other issues to consider" that is your job. We just want >> the feature. We don't really care what it takes. > > I'm sure we're all waiting to see YOUR compiler/debugger product, Frank. > > /alastair/ I guess what alastair is saying here is if we know of a feature that would improve a product, our only option to getting that feature is to produce our own product. Interesting. Is this the general sentiment of others on the net? I would like to reiterate (and others on the net have also pointed this out) that this is NOT an unusual feature for a debugger to have. I have used debuggers (on other platforms) that have this feature and it is VERY useful. I would also like to say that I think the THINK product is generally a pretty good one. I just think that adding this feature to the debugger would make it more useable (i.e. better), that's all. When I say it is "doable" I'm NOT saying "I could write a compiler/debugger that could do this", what I'm saying is that OTHER compiler/debugger vendors HAVE done this, and I imagine that the talented people at THINK could probably do it, too. -- Frank Owen 312-982-2182 AT&T Bell Laboratories 5555 Touhy Ave., Skokie, IL 60077 PATH: ...!att!ihc!fjo