|
The STRISDB mode is more like that of, say, Visual Basic's watch - you can see the values every time you stop at any statement. There's no way in STRDBG to see the values as you go, without F11 or eval. The watch there is like a breakpoint whenever something changes - a different way to think of a watch. Of course, you can always do conditional breaks. The STRISDB kind of watch would save me from having to do a bunch of EVALs. > Isn't that the whole purpose of a 'watch', to know when a variable changes? > STRDBG tells you when it changes so that you don't have to watch it on the > screen at every step. I actually have come to like the STRDBG way although > I did have to get used to it. > > Scott Mildenberger > > > -----Original Message----- > > From: vhamberg@attbi.com [mailto:vhamberg@attbi.com] > > Sent: Thursday, July 11, 2002 9:07 AM > > To: midrange-l@midrange.com > > Subject: RE: STRISDB debugger - was RE: CPW=0 and one session? > > > > > > That's right - that's the one thing I miss the most, I > > think. You can set watches in the STRDBG version, but > > you don't see them at envery step, they only do > > something when a variable changes. > > > _______________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.