× 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: R: RPG Indicators
  • From: boldt@xxxxxxxxxx
  • Date: Thu, 20 Apr 2000 09:11:37 -0400



Anton wrote:
>Maybe there's an "internal" field like for the null indicator that
>can be debugged?
>The latter can be found in the RPG manual and fieldname starts with
>QRNU if i remember it correctly.
>It would not be surprised if there was something similar for these
>%BIFs, too.
>
>Is there? If not, such fields would do!

Sorry, for almost all BIF's, there is no "internal" field
that can be debugged.  In some cases, the BIF simply results
in a value pushed on the run-time stack.  In others, the
result is placed in some compiler generated temporary (or set
of temporaries), but the name is not debuggable.  Even if
these temps were debuggable, the temps are re-used, sometimes
even within the same statement.  As I said before, substantial
work would be needed in both the compiler and debugger to
allow debugging of BIF results, so this is not likely to
happen.

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com


+---
| 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.