JJ Allaire
July 1st, 2013
Greater Boston useR Group
Phase 1: Seamless integration with existing R debugging tools (browser, recover, traceback, etc.)
Phase 2: Setting breakpoints in the editor; smooth transitions from runtime errors into debugging tools
str
Governed by the global “error” option, which is NULL
by default:
options(error = NULL)
Either a function or an expression governing the handling of non-catastrophic errors such as those generated by stop as well as by signals and internally detected errors. If the option is a function, a call to that function, with no arguments, is generated as the expression.
options(error = traceback)
Prints the call stack of the last uncaught error, i.e., the sequence of calls that led to the error.
Is often enough to understand the source of an error
options(error = browser)
Interrupt the execution of an expression and allow the inspection of the environment where browser was called from.
options(error = recover)
Allows the user to browse directly on any of the currently active function calls via an interactive menu.
The built in R debugging tools are powerful and flexible, so the first order of business is to provide seamless integration with those tools
What does that mean? Let's take a look….
browser()
function to hit a breakpoint anywheresource()
Title Slide
===================
author: John Doe
date: Feb 7th, 2013
Slide w/ Bullets
===================
- Bullet 1
- Bullet 2
- Bullet 3
Slide with Code
===================
```{r}
summary(cars)
```
Code w/o Evaluation
===================
```{r, eval=FALSE}
summary(cars)
```
Output Only Slide
===================
```{r, echo=FALSE}
summary(cars)
```
Plot Slide
===================
```{r, echo=FALSE}
plot(cars)
```
Slide with Columns
===================
First column
***
Second column
Slide with Columns
===================
left: 70%
First column
***
Second column
Download the v0.98 preview release at:
http://www.rstudio.com/ide/download/preview
Slides for this talk are at: