Re: %EOF, %FOUND and the infamous Dow loop

[Douglas Handy <dhandy1@xxxxxxxxxxxxx>]

John,

>I too would like to be able to say
>
>EVAL %EOF(FILE)

It would be great to be able to give it any function or procedure name and have
it display the return value, not just certain BIFs...

>and
>
>EVAL %EOF(FILE) = '1'

I'm not convinced that the ability to set what should be the return value for a
function, BIF or not, is a road we should go down.

>( also wonder what to do with problems like,  What does;
>
>EVAL %EQUAL = '1'
>
>mean ?  If it is the result of a lookup, the lookup still failed right?

Yup, and if a READx failed you still don't have a valid open data path position
etc.  The point being it is not a real-life test of how the code reacts when you
alter a status flag without altering the other things it impacts under the
covers.

I'd agree the ability to display the return value of a BIF and even user defined
function from the debug command line would be welcome.

Attempting to make the debugger accept a function (including BIF) on the *keft*
side of the equal sign seems like a Pandora's box.  IMHO.

Doug