× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: working with the value of integer variables in debug
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Tue, 11 May 1999 17:54:07 -0400

Heh!  Those temporary areas are called indicators.  I would assume that the
official answer is that if you're debugging and you have an if %found() you
could break inside the if block instead of setting a conditional break on
the if %found() itself.

Buck Calabro

> -----Original Message-----
> From: Rob Berendt 
> Sent: Tuesday, May 11, 1999 4:51 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: working with the value of integer variables in debug
> 
> Possible work arounds include storing the results of %founds and whatnots
> into temporary 
> variables, (at least during debugging).  Example:  eval filestatus =
> %found(filename).  
> Another workaround is to use indicators instead of %found.  If IBM wanted
> you to use bif's 
> they'd support them in the debugger, (just sarcasm).
> 
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.