From pgilbert@bank-banque-canada.ca  Thu May 14 16:21:56 1998
From: pgilbert@bank-banque-canada.ca (Paul Gilbert)
Date: Thu, 14 May 1998 11:21:56 -0400
Subject: error trapping
Message-ID: <98May14.112731edt.13594@mailgate.bank-banque-canada.ca>

One thing I've found missing in S/R is the ability to test error trapping. I
have written a fairly extensive set of tests for my time series library but I
can only test that things work for cases where they are suppose to work. In
several places my code is suppose to recognize error conditions, like invalid
inputs, and make calls to stop() or warn(), but there is no automatic way to
check these in my test suite.

I really would like to be able to write a code testing program which would be
able to specify that I am about to generate a "stop" condition with a given
message, then do it, then continue, accepting that that was the right result.

This is not a high priority, but it is worth keeping on the wish list.

Paul Gilbert

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._


error trapping
Paul Gilbert