- From: Gary Scott <garylscott@xxxxxxxxxxxxx>
- Date: Fri, 19 Sep 2008 11:46:20 -0500
Here's what I need in a "final" procedure.
Of course normal termination isn't a problem, but I have various I/O boards that I need to ensure are properly terminated/safed (put in a known state (e.g. not transmitting, outputs reconfigured to inputs) in the event of a program crash. This is in part to ensure that transmitters aren't overheated from prolonged operation (e.g. stuck in the xmit state) or shorted because someone starts dismantling the test setup thinking that the devices are automatically safed upon program crash.
How is that handled normally? Will any of the new f2k3, f2k8 features help me in this area (fault detection/recovery)?
mailto:garylscott@sbcglobal dot net
Fortran Library: http://www.fortranlib.com
Support the Original G95 Project: http://www.g95.org
Support the GNU GFortran Project: http://gcc.gnu.org/fortran/index.html
If you want to do the impossible, don't hire an expert because he knows it can't be done.
-- Henry Ford
- Prev by Date: Re: DATA statement to initialise arrays
- Next by Date: Re: PASSING ARRAY FORTRAN DLL TO/FROM VBA EXCEL
- Previous by thread: PASSING ARRAY FORTRAN DLL TO/FROM VBA EXCEL
- Next by thread: Re: "Final" Procedures