Tidy-up error handling in Rput_RGet

hodgesse1 / rfortran

Automatically exported from code.google.com/p/rfortran

0 stars 0 forks source link

Tidy-up error handling in Rput_RGet #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Currently Rget(r_var,fortran_var,alloc=.true.) returns an ok !=0 if there
is a size mismatch between fortran_var and r_var

Better to provide more informative error message using
call message($error,"msg") with what actual problem is and what variables
are involved

Original issue reported on code.google.com by mark.th...@gmail.com on 4 Jun 2009 at 5:29

GoogleCodeExporter commented 8 years ago

Update to the error messages for Rput, Rget should include the following:

* Return an informative error messages with likely cause and R_var name
* All errors from StatConnector get routed through error_msg to decode error 
number
* error_msg containsfull list of errors from
file:///C:/Program%20Files/statconn/DCOM/doc/DCOM.html

Original comment by mark.th...@gmail.com on 4 Jun 2009 at 11:54

Changed title: _Tidy-up error handling in Rput_RGet _

GoogleCodeExporter commented 8 years ago

Original comment by mleon...@civeng.adelaide.edu.au on 9 Jun 2009 at 7:13

Added labels: Priority-minor

GoogleCodeExporter commented 8 years ago

Original comment by mleon...@civeng.adelaide.edu.au on 9 Jun 2009 at 7:14

Added labels: Priority-major

GoogleCodeExporter commented 8 years ago

Original comment by mleon...@civeng.adelaide.edu.au on 9 Jun 2009 at 7:29

Added labels: Component-Core, Milestone-Future

GoogleCodeExporter commented 8 years ago

Original comment by mleon...@civeng.adelaide.edu.au on 9 Jun 2009 at 7:31

Added labels: Severity-hours

GoogleCodeExporter commented 8 years ago

I'd like to get this finished for Release 1.0. If we do it now, we can leave it 
for a
long time

Original comment by mark.th...@gmail.com on 9 Jun 2009 at 12:07

Added labels: Milestone-Release1.0
Removed labels: Milestone-Future

GoogleCodeExporter commented 8 years ago

Fixed in version 2.0.0

Original comment by mark.th...@gmail.com on 19 Feb 2010 at 5:24

Changed state: Fixed