I am a happy user of ESS for coding and debugging R code. I have found a elusive bug recently deeply inside several for loops and ifs structures.
我是ESS的快樂用戶,用於編碼和調試R代碼。我最近在幾個for循環和ifs結構中發現了一個難以捉摸的bug。
Is there any way of having ESS selectively travel the if/else structures or loop for all the values in a for loop?.
有沒有辦法讓ESS有選擇地移動if / else結構或循環for for循環中的所有值?
Does R or ESS have debugger mode where you can skip else clauses, loop the values and step into, step through, return etc?
R或ESS是否具有調試器模式,您可以跳過else子句,循環值並逐步進入,逐步執行,返回等?
[UPDATE]
[UPDATE]
Thanks @jubba for the link to the other SO question about debugging tools for R-language. At the end this was my real question. This other thread give the links for the kind of things that I wanted to know about the way of doing debugging in the current R.
感謝@jubba鏈接到另一個關於R語言調試工具的SO問題。最后,這是我真正的問題。這個其他線程提供了我想知道的關於在當前R中進行調試的方式的事情的鏈接。
8
There has been a more general question about debugging in R on Stackoverflow :
有關在Stackoverflow上調試R的一般問題:
Debugging tools for the R language
R語言的調試工具
One answer by Davor Cubranic points to ess-tracebug
which is, according to its website, "An emacs package for interactive debugging and error tracing in ESS". I've never used it myself, but it may be useful to you :
Davor Cubranic的一個答案指向ess-tracebug,根據其網站,“用於ESS中的交互式調試和錯誤跟蹤的emacs包”。我自己從未使用它,但它可能對您有用:
http://code.google.com/p/ess-tracebug/
http://code.google.com/p/ess-tracebug/
本站翻译的文章,版权归属于本站,未经许可禁止转摘,转摘请注明本文地址:https://www.itdaan.com/blog/2011/02/23/72545ce385b9e3274b5d6f12c280f231.html。