 |
forums.silverfrost.com Welcome to the Silverfrost forums
|
View previous topic :: View next topic |
Author |
Message |
silicondale
Joined: 15 Mar 2007 Posts: 252 Location: Matlock, Derbyshire, UK
|
Posted: Fri Aug 09, 2013 12:45 pm Post subject: Full list of exceptions? |
|
|
I am most of the way to getting a robust Fortran system for web delivery of a set of applications (using Win32, not .Net), but I need to be sure that I have a FULL list of all possible exceptions. Just got caught out by INTEGER OVERFLOW, exception 15, omitted from the TRAP_EXCEPTION@ documentation in the latest version of the FTN95 help file.
Are there any other exceptions that are also undocumented?
I'm using PERMIT_UNDERFLOW@ but treating all other exceptions as unrecoverable, and really need to catch them all, as a dialog window on a web server will hang the server as there is no way to either display or respond to it.
I'm also using the /CHECK and /ZEROISE compiler options.
ps - is there any Win32 equivalent to the exception generator example for .Net that is given in the FTN95 help file? I have found an old set of demo programs for CHECKMATE from an old Salford Fortran installation, but this is far from complete. How can I force an access violation, for example? _________________ (Steve Henley) |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8210 Location: Salford, UK
|
Posted: Fri Aug 09, 2013 2:39 pm Post subject: |
|
|
All of the exception numbers are listed in exceptn.ins.
I would have expected PERMIT_UNDERFLOW@ to be the default.
The statement
generates and access violation.
In most cases you can not recover from an exception. There is no TRY and CATCH. So programs should be written carefully and tested before release.
/CHECK etc are intended for testing and development, not for release. |
|
Back to top |
|
 |
silicondale
Joined: 15 Mar 2007 Posts: 252 Location: Matlock, Derbyshire, UK
|
Posted: Fri Aug 09, 2013 3:30 pm Post subject: |
|
|
Thanks, Paul.
If except.ins is complete, then I have them all now - thanks. It was only integer overflow (15) that was missing.
I am not trying to recover from exceptions, but what I do need is to trap them, write a simple error message to the standard output stream, and exit cleanly. No need even to save the current state of user data, as they would need to restart the program from original input data in any case. I just need to prevent unexpected (indeed any!) dialog windows, which can't be handled on a web server. _________________ (Steve Henley) |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|