× 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: Displaying functional value in debug
  • From: bmorris@xxxxxxxxxx
  • Date: Tue, 25 Jul 2000 15:24:53 -0400




>Date: Mon, 24 Jul 2000 11:09:43 -0400
>From: Buck Calabro <buck.calabro@aptissoftware.com>
>
>Sorry, it can't be done, and it's a bit depressing.  More valuable to me
>would be the ability to set/reset these BIFs.  About the only way to deal
>with the situation is to use a flag to indicate the value (can you say
>indicator?  :-) )

I know that people were accustomed to displaying and changing the
result indicators on I/O operations in the debugger.  Wishing for the
debugger to support displaying a builtin function is reasonable.
(You can ask, but you won't get.  Some of the feedback bifs do just
return simple variables, but others require code-generation using
compiler internals to calculate the value.  Duplicate this in the
debugger would be impossible.)

These BIFs are not just syntactic replacements for indicators.  They
are functions, and you can't ever set and reset a function; you can
only call it.

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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.