Is there anyway (other than 'repeat'') of catching the errors that R throws? Thanks, ------------------- Barnet Wagman wagman at enteract.com 773-645-8369 1361 N. Hoyne Chicago, IL 60622 -------------------- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help 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-help-request at stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
Catching errors?
2 messages · Barnet Wagman, Robert Gentleman
On Sun, 25 Apr 1999, Barnet Wagman wrote:
Is there anyway (other than 'repeat'') of catching the errors that R throws? Thanks,
I'm not sure what you mean by "catch". I don't think that repeat catches anything. If you want to know where you were when the error occured then traceback(), immediately after the error will provide you with the call stack. You can use debug and browser to try to track it down. If on the other hand hand you're asking about a "real" error catching mechanism, then the answer is no. I am working on improving the current state of affairs somewhat and there is some potential for error catching but it may involve a large amount of rewriting of the code to make it safe to do so though. If you could provide a concrete example of what you want it would be easier for people to help you. -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help 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-help-request at stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._