[R] Debugging R's code: boxplot.stats

Gabor Grothendieck ggrothendieck at gmail.com
Sat Oct 28 05:19:37 CEST 2006


The edit operations does not change the boxplot.stats that you
are debugging.  It creates a new boxplot.stats (i.e. now there
are two) and the new one does not have debugging turned on.
Try

getAnywhere("boxplot.stats")

and it finds two.  If you remove the one you just created using rm debugging
reappears since you are now accessing the original one for which
debugging is still on.  If you like you can turn debugging on in the
new one.

On 10/27/06, Matthew Walker <m.g.walker at massey.ac.nz> wrote:
> Hi everyone,
>
> I think I have found a minor issue with the R function "boxplot.stats".
> But before I make such a rash comment, I'd like to check my facts by
> fixing what I think is the problem.  However, why I try to do this, R
> does not behave as I expect.  Can you tell me what I'm doing wrong?
>
> If I use the command:
> debug(boxplot.stats)
> I am allowed to step through the code as normal.
>
> I then want to edit the function, so I type:
> boxplot.stats <- edit(boxplot.stats)
> and I make my changes.
>
> I can check my changes have been made by typing:
> boxplot.stats
> and the updated version appears on screen.
>
> But now when I come to test my changes, the "debug" functionality has
> just up and disappeared; I can no longer step though the function as
> normal.  Further to that, it appears that the change has somehow not
> been registered, as exactly the same error occurs---although I cannot be
> sure that it is occurring inside boxplot.stats.
>
> Does anyone have any tips, suggestions or comments?  I'd love to be able
> to fix this.
>
> (For what it's worth I wish to change line 14 of boxplot.stats so that
> it reads "if (any(out[nna],na.rm=TRUE))".)
>
>
> Thank you for your thoughts,
>
> Matthew
>
> ______________________________________________
> R-help at stat.math.ethz.ch mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>



More information about the R-help mailing list