Re: [Rd] debuggingState() analogous to tracingState() ?

2014-10-02 Thread Mark.Bravington
Just FYI: the 'debug' package lets you set a stop-before-exit, and of course the ability to adjust breakpoints while the function is running. You can get the current return value via 'get.retval()'. There is some rough-edged support for debugging scripts, too. Mark Mark Bravington CSIRO CMIS M

Re: [Rd] debuggingState() analogous to tracingState() ?

2014-10-02 Thread Stephan Wahlbrink
The possibility to temporarily turn off debugging sounds interesting. A short comment at the end Am 2014-10-02 um 16:55 schrieb Martin Maechler: We have had some conversation within R core, lead by Duncan Murdoch and me, about a proposal to extend the current tracingState() functionality by s

Re: [Rd] debuggingState() analogous to tracingState() ?

2014-10-02 Thread Jonathan McPherson
> > > I don't have much of an opinion on these questions. I've never used the > > tracingState() function, though I use trace() all the time (via > > setBreakpoint()). You might want to consult people who write debugger > > front-ends. > > which I am now doing: I'm including ESS-core, > Jonat

Re: [Rd] debuggingState() analogous to tracingState() ?

2014-10-02 Thread Duncan Murdoch
On 02/10/2014 11:55 AM, Richard M. Heiberger wrote: Interesting timing. I could have used this additional control yesterday in class. I am teaching a graduate Statistical Computing class. Last night I went through the symbolic deriviatives (the deriv and D functions) in Section 9.6 of the Blue

Re: [Rd] debuggingState() analogous to tracingState() ?

2014-10-02 Thread Richard M. Heiberger
Interesting timing. I could have used this additional control yesterday in class. I am teaching a graduate Statistical Computing class. Last night I went through the symbolic deriviatives (the deriv and D functions) in Section 9.6 of the Blue Book. The D function is recursive. I illustrated it

Re: [Rd] Intel Fortran compiler returns a -1 TRUE value

2014-10-02 Thread Ei-ji Nakama
Hello > The value generated by Fortran's .TRUE. evaluates as "truthy" -- as in > all(z[[1]]) -- but is neither equal to nor identical to TRUE. Its numeric > conversion to -1 is most unusual, every other system I've tried converts to > +1. Please read the -fpscomp logicals option of ifort. -- "\u

Re: [Rd] debuggingState() analogous to tracingState() ?

2014-10-02 Thread Martin Maechler
We have had some conversation within R core, lead by Duncan Murdoch and me, about a proposal to extend the current tracingState() functionality by something tentatively called debuggingState(). Duncan has allowed me to copy the previous conversation (after very minor editing): The following is