search

hodgesse1 / rfortran

Automatically exported from code.google.com/p/rfortran
0 stars 0 forks source link

another instance of fragile error handling in Rinit #74

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
*** If you have a coding solution to this defect please include the file
(or preferably a svn patch) as an attachment

See attached

*** Please provide any additional information below.

Need better distinction between fatal and non-fatal errors and more judicious 
use of function output values when the code is peppered with premature RETURNs

Original issue reported on code.google.com by dmitri.k...@gmail.com on 22 Jun 2010 at 8:19

Attachments:

GoogleCodeExporter commented 8 years ago 
a new variable "nonFatalErr" has been added to Rinit programming to catch 
errors which have alternative work-arounds

Original comment by mark.th...@gmail.com on 13 Feb 2011 at 2:14