RE: File Exception/Error Subroutine - INFSR

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>*every*, I/O operation involving a data
>file is checked with %error.
-snip-
>I just would desire to "hide" the code in a
>faraway routine
-snip-
>Does anyone have practical experience using INFSRs?

Yes.  They are great for catching unexpected errors (like object damage),
doing a post-mortem DUMP and exiting with an error code set so the caller
can handle the fact that this program failed.  Great for commitment control.

As you note, you can't resume at the point of failure.  For more information
on that, check the MONITOR operation.  This very list had a thread on this
topic not too long ago.

Whatever you decide to do, I might argue that you should keep the I/O and
it's error handling together.  To me, that means wrapping the I/O in either
a subr call or a procedure call.  I prefer a subr because it is very clear
to me that subrs deal with global variables (like file fields.)
  --buck