Re: [Rd] callCC in 2.7.0
> Would anyone like to explain if callCC in R 2.7.0 gives > anything that on.exit does not already provide? > > It seems that the exit condition once defined cannot > be added to overridden whereas with on.exit multiple > on.exit's add additional on.exits rather than being ignored. > > Is this important? It facilitates a completely different style of programming - see http://en.wikipedia.org/wiki/Continuation-passing_style -- http://had.co.nz/ __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] Wishlist: browser and traceback should trim callstack when printing (PR#8638)
Full_Name: Hadley Wickham Version: 2.2.0 OS: OS X Submission from: (NULL) (129.186.195.213) Example: f <- function(...) browser() do.call(f, mtcars) Entire contents of mtcars is printed on callstack. When you are using do.call with large data.frames this is a frustrating as it easily wipes out your entire buffer. While it is useful to be able to see all the arguments when looking for the cause of the bug, manual inspection is impractical when dealing with very long arguments. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
