| Line 15... |
Line 15... |
| 15 |
\details{
|
15 |
\details{
|
| 16 |
When a function flagged for debugging is entered, normal execution
|
16 |
When a function flagged for debugging is entered, normal execution
|
| 17 |
is suspended and the body of function is executed one statement at a time.
|
17 |
is suspended and the body of function is executed one statement at a time.
|
| 18 |
A new browser context is initiated for each step (and the previous one
|
18 |
A new browser context is initiated for each step (and the previous one
|
| 19 |
destroyed).
|
19 |
destroyed).
|
| 20 |
Currently you can only debug functions that have bodies enclosed in braces.
|
- |
|
| 21 |
This is a bug and will be fixed soon.
|
- |
|
| 22 |
% -when was this "soon" written? [MM. 1998.9.4]
|
- |
|
| 23 |
You take the next step by typing carriage return, \code{n} or \code{next}.
|
20 |
You take the next step by typing carriage return, \code{n} or \code{next}.
|
| 24 |
You can see the values of variables by typing their names.
|
21 |
You can see the values of variables by typing their names.
|
| 25 |
Typing \code{c} or \code{cont} causes the debugger to continue to the
|
22 |
Typing \code{c} or \code{cont} causes the debugger to continue to the
|
| 26 |
end of the function.
|
23 |
end of the function (or loop if within a loop).
|
| 27 |
You can \code{debug} new functions before you step in to them from inside
|
24 |
You can \code{debug} new functions before you step in to them from inside
|
| 28 |
the debugger.
|
25 |
the debugger.
|
| 29 |
Typing \code{Q} quits the current execution and returns you to the
|
26 |
Typing \code{Q} quits the current execution and returns you to the
|
| 30 |
top--level prompt.
|
27 |
top--level prompt.
|
| 31 |
Typing \code{where} causes the debugger to print out the current
|
28 |
Typing \code{where} causes the debugger to print out the current
|
The R Project SVN
R