similar to: new version of package:debug

Dear R users New versions of the 'mvbutils' and 'debug' packages are now available on CRAN, both in source form and as precompiled binaries. 'mvbutils' offers the following (as well as many miscellaneous utilities): ? hiearchical, searchable project organization, with workspaces switchable inside a single R session, and objects in "ancestor" projects always

Dear R users New versions of the 'mvbutils' and 'debug' packages are now available on CRAN, both in source form and as precompiled binaries. 'mvbutils' offers the following (as well as many miscellaneous utilities): ? hiearchical, searchable project organization, with workspaces switchable inside a single R session, and objects in "ancestor" projects always

New versions of the 'mvbutils' and 'debug' packages are now available on CRAN. These should work with R 2.10 as well as R 2.9. 'mvbutils' offers tools for organization of workspaces, function/documentation editing with backups, package construction and updating, seamless per-object lazy-loading, and various miscellaneous goodies. New in this version: nearly-automated

New versions of the 'mvbutils' and 'debug' packages are now available on CRAN. These should work with R 2.10 as well as R 2.9. 'mvbutils' offers tools for organization of workspaces, function/documentation editing with backups, package construction and updating, seamless per-object lazy-loading, and various miscellaneous goodies. New in this version: nearly-automated

Version 1.2.2 of 'debug' is now on CRAN. The debugging facilities offered include code display, graceful error recovery, line-numbered conditional breakpoints, access to exit code, flow control, and full keyboard input. The new version supports debugging of code inside 'try', 'eval', 'evalq', and 'with' statements. See package?debug for more info. -- Mark

Version 1.2.2 of 'debug' is now on CRAN. The debugging facilities offered include code display, graceful error recovery, line-numbered conditional breakpoints, access to exit code, flow control, and full keyboard input. The new version supports debugging of code inside 'try', 'eval', 'evalq', and 'with' statements. See package?debug for more info. -- Mark

Dear group I use "restart" in part of my code, in a way that's not easily changed to "try". As I convert code from R1.5.0 to R1.6.1, I'm getting ugly messages; the help system says to contact r-devel, so here I am. This one's a bit complicated-- sorry! The context is inside a debugger (I have an R and S debugger that offers stand-alone code windows, line numbered

Dear list, I received the response below from the package author of 'debug'. I post it to the list, with Mark's approval, in case it is useful to others too. Regards, Matthew -----Original Message----- From: Mark.Bravington at csiro.au [mailto:Mark.Bravington at csiro.au] Sent: 22 October 2006 23:53 To: Matthew Dowle Cc: Mark.Bravington at csiro.au Subject: RE: Debug package

Please use the CRAN versions, not the ftp versions which are now out-of-date. Both packages are on base CRAN now, but may not have propagated to all mirrors yet. (But thanks to Gerald for responding-- I had de-subscribed from R-help.) For anyone using the HANDY package (a Windows-specific package which includes a non-C DLL, so I can't CRAN it): I'll post an updated version on the ftp site

There is a new version of the 'mvbutils' package (v1.1.1) available on CRAN. For existing users, the main new features are: (i) 'help' now works properly with with R2.0+ (!) (ii) 'mvbutils' is now NAMESPACEd, so you can avoid naming conflicts with other packages. (Many functions are no longer user-visible. (iii) Lazy-loading of individual objects is now available. Among

There is a new version of the 'mvbutils' package (v1.1.1) available on CRAN. For existing users, the main new features are: (i) 'help' now works properly with with R2.0+ (!) (ii) 'mvbutils' is now NAMESPACEd, so you can avoid naming conflicts with other packages. (Many functions are no longer user-visible. (iii) Lazy-loading of individual objects is now available. Among

Hi Jannis [I'm the author of package debug... I know this is 6 months after your query, sorry-- but I don't subscribe to R-help, and you didn't post to the maintainer! I'm primarily sending this to close off the thread.] > when I use the package debug, mark a function with mtrace() and enter > into the browser like mechanism of debug a window displaying the code of >

Wolski wrote: #>>>Has anyone a tool which is able to generate from #>>>#appropriately commented R-code files (e.g. <<example>>= #>>>#-example section) Rd files: Mark Bravington mentioned something similar in the 'mvbutils' package: Wolski wrote: # # #Hi! # #Is it working with S4? Mark's reply: Don't know whether it works with S4

On Fri, Apr 10, 2020 at 2:42 AM Bravington, Mark (Data61, Hobart) <Mark.Bravington at data61.csiro.au> wrote: > > > On Thu, Apr 9, 2020 at 12:44 PM Bravington, Mark (Data61, Hobart) > > <Mark.Bravington at data61.csiro.au> wrote: > > > > > > The "r-devel snapshot build" 78175 on Windows--- a dot-exe installer--- seems to be missing a couple of

Hi Mark: I had also used sample and tabulate for generating multinomial and found it to be quite slow. So I had written a multinomial random numbers generator based on the GENMUL subroutine from "ranlib", which in turn is based on the algorithm from Luc Devroye's book on "Non-Uniform Random Variate Generation" You may want to compare this with your hybrid algorithm and

Thanks-- as Duncan Murdoch also noted, R_HISTFILE can be used to solve my problem, as below. BTW it's not easy to find out about R_HISTFILE in the help system or manuals, though, unless you already know it exists-- it only seems to be described under startup options, not things to do with history. However, Duncan's reply did hint at an inconsistency, in that savehistory() defaults to

'getAnywhere' is not reporting methods when there are periods in the class name or the generic name (in R-devel). > getAnywhere( 'predict.loess') A single object matching 'predict.loess' was found It was found in the following places registered S3 method for predict from namespace modreg namespace:modreg with value <<...>> > getAnywhere(

>>>>> Jeroen Ooms >>>>> on Fri, 10 Apr 2020 08:54:39 +0200 writes: > On Fri, Apr 10, 2020 at 2:42 AM Bravington, Mark (Data61, > Hobart) <Mark.Bravington at data61.csiro.au> wrote: >> >> > On Thu, Apr 9, 2020 at 12:44 PM Bravington, Mark >> (Data61, Hobart) > <Mark.Bravington at data61.csiro.au>

lib.fixup My previous post mentions a problem encountered when calling ".Internal( lib.fixup..." in R1.5.0. I have since found a workaround. It's possible in R1.5.0 to set attributes of search path environments directly, like so: > env_ pos.to.env( 3) > attr( env, 'any.attr')_ 'any.value' > pos.to.env( 3) <environment: package:tcltk>

I noticed that, in R1.9.0 beta where the old 'base' package has been split into 4, '.First' gets executed with just the new 'base' loaded, before 'stats' 'utils' and 'graphics' are available. The NEWS file does warn that this will be the case for .Rprofile, but doesn't mention .First. Is this actually the intended behaviour where .First is