Re: [R] getting informative error messages

From: Tony Plate <>
Date: Fri, 11 May 2007 11:12:52 -0600

Prof Brian Ripley wrote:
> It is not clear to me what you want here.

I just wanted to be able to quickly find the expression in which an error occurred when it was inside a lengthy function. I now know that 'debug()' can help with this (debug() allows me to easily step through the function and see where the error occurs.)

> Errors are tagged by a 'call', and f(1:3) is the innermost 'call' (special 
> primitives do not set a context and so do not count if you consider '[' 
> to be a function).

Thanks for the explanation. I suspected that it had something to do with primitive functions, but was unable to confirm that by searching.

> The message could tell you what the type was, but it does not and we have 
> lost the pool of active contributors we once had to submit tested patches 
> for things like that.

What is required to test patches for things like this? Is there anything written up on that anywhere? I've not been able to clearly discern what the desired output of 'make check' is -- there seem to be reported differences that don't actually matter, but I didn't see a fast and easy way of distinguishing those from the ones that do matter. I did look in R-exts, and on but was unable to find clear guidance there either. mailing list PLEASE do read the posting guide and provide commented, minimal, self-contained, reproducible code. Received on Fri 11 May 2007 - 17:17:26 GMT

Archive maintained by Robert King, hosted by the discipline of statistics at the University of Newcastle, Australia.
Archive generated by hypermail 2.2.0, at Mon 14 May 2007 - 15:01:29 GMT.

Mailing list information is available at Please read the posting guide before posting to the list.