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



Doug,

Sorry, gotta agree with Joe on this one.

jt



| -----Original Message-----
| Behalf Of Douglas Handy
| Sent: Sunday, December 30, 2001 5:50 PM

<snip>

|
| The basic problem is that the BIF's are *functions*, not data values.  The
| debugger can display the value of any variable, *INxx or
| otherwise, but cannot
| display the value of any function, %BIF or otherwise.
|

<snip>

| The times I have used it and needed to debug, single stepping
| works for me.

Not as good.

|
| How is it that not being able to display the result of a BIF is
| "taking away
| functionality"?

I think Joe's saying that the %BIF is less effective than an indicator.

I would think it WOULD take only a couple hours.  They change the
implementation of the %BIF to us a memory location instead of a register, if
it's not already that way.

You allow both the language and the debugger:  EVAL %BIF = *ON.  If these
are already stored in memory locations (ie variables) then it's just a
matter of assigning a value to a named variable.


I'll be glad to stand corrected.  But I'd still like to see this fixed.
It's broke, IMHO, because the %BIF should be at least as effective as *IN,
if they want you to go towards eliminating indicators.

jt



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.