On 10/23/2009 2:49 PM, Andrew Yee wrote:
Thanks everyone for the responses. As a suggestion, wouldn't it be useful,
that when you run isdebugged() without any parameters, it would just report
back the functions that are being flagged for debugging?
Could you give an example of what the answer would look like? Not all
functions have names, not all names are unique, ...
Duncan Murdoch
Andrew
On Fri, Oct 23, 2009 at 2:12 PM, Yihui Xie <xieyi...@gmail.com> wrote:
Oops... I forgot to mention that 'envir' (or 'pos') should be
specified in ls()/get() in my last reply if you are looking for
debugged functions in environments other than ".GlobalEnv".
Regards,
Yihui
--
Yihui Xie <xieyi...@gmail.com>
Phone: 515-294-6609 Web: http://yihui.name
Department of Statistics, Iowa State University
3211 Snedecor Hall, Ames, IA
On Fri, Oct 23, 2009 at 1:02 PM, Duncan Murdoch <murd...@stats.uwo.ca>
wrote:
> On 10/23/2009 1:28 PM, Andrew Yee wrote:
>>
>> This is kind of a dumb question: I know you can use isdebugged() to
find
>> out if a specific function is flagged for debugging, but is there a way
to
>> list all the functions that are flagged for debugging?
>
> No, R doesn't keep any master list, it sets a flag in each one. So you
> could iterate over all visible objects to find the ones that have the
flag
> set (and this is quite slow, there are a lot of places to look), but
there
> would always be the chance that one was hiding somewhere you didn't look.
>
> Duncan Murdoch
>
> ______________________________________________
> R-help@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>
______________________________________________
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
