similar to: checking for _non-existing_ documentation entries.

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

I noticed the following today --- str() seems to remove any extra class information added to an environment. > e <- new.env() > class(e) [1] "environment" > class(e) <- c("foo", class(e)) > class(e) [1] "foo" "environment" > str(e) Classes 'foo', 'environment' length 0 <environment> > class(e) [1]

I am another person who has had trouble documenting S4 classes and (particularly) methods. The methods package itself is pretty cool by the way, but it is a pity that there are as yet no guidelines on S4 in the "Writing R Extensions" document. I have actually put together a guide on S4 documentation myself for the use of my own lab which is at

# r-bugs@r-project.org `predict' complains about new factor levels, even if the "new" levels are merely levels in the original that didn't occur in the original fit and were sensibly dropped, and that don't occur in the prediction data either. (At least if `drop.unused.levels' was set to TRUE, which the default.) test> scrunge.data.2_ data.frame( y=runif( 3),

Dear r-users! I wonder if there is a way of designing a directory like structure for holding my data using environments? It would be nice if I could implement a kind of 'cd' command to change to a differend environment etc. Can anybody give me a hint? -cl -- Christoph Lange MPI fuer biologische Kybernetik |Phone: +49-7071-601-607| Postfach 2169, D-72012 Tuebingen |FAX:

Hi the devel list. I am adapting the package.skeleton to S4 classes and methods I would have been very proud to post a new working function on this list. Unfortunately, I do not manage to solve all the problems. Mainly - sys.source does not compile a file with setClass - dumpMethod does not exists yet In the following code, thise two problems are notified by a line ################# Still

A new version of the package has been committed to the r-devel branch. There are a lot of changes, mostly non-visible, many of those to tighten up some possible problems. For example, slot assignment now checks the validity of the value being assigned, and basic classes cannot be overriden. There is a version of the promptClass function by Vince Carey, to produce shell of documentation for a

I've been looking at documenting S4 classes and methods, though I have a feeling many of these issues apply to S3 as well. My impression is that the documentation system requires or recommends creating basically the same information in several places. I'd like to explain that, see if I'm correct, and suggest that a more automated framework might make life easier. PROBLEM Consider a

# # r-bugs@r-project.org # ###################################################### Because I work in different directories, but always want to save my .Rhistory in the same place, I have changed the system function savehistory to this: function (file = "D:/R50/.Rhistory") invisible(.Internal(savehistory(file))) When I use q() to quit R, and it asks me whether I want to

Hi! Have written some functions with signature "numeric". eg. setGeneric("foo", function(object,...) standardGeneric("foo")) setMethod("foo",signature(object="numeric"),def = .... To generate the Rd file sceleton i use > promtClass("numeric") A shell of class documentation has been written to the file

Dear list members, I've been puzzling over how best to clean up the code for my Rcmdr package. In particular, there's a lot of repetitive tcltk code in the package, and as Martin M?chler has pointed out to me, this makes the package difficult to maintain. If R were Lisp, I'd use macros for much of the clean up. My efforts to do similar things with R functions has run into problems

1. I'm putting together my first package that uses S4 classes and objects. I'd like to document them, but I'm not sure what the documentation should look like, and package.skeleton doesn't produce any at all for the classes or methods. Are there any good examples to follow? 2. How do I do the equivalent of debug(foo), when foo is an anonymous function being used as a method?

promptClass fails to identify methods associated with the class. Here is a fix: Index: promptClass.R =================================================================== --- promptClass.R (revision 41719) +++ promptClass.R (working copy) @@ -165,7 +165,7 @@ if (nmeths > 0) { .meths.body <- " \\describe{" for (i in 1:nmeths) { - .sigmat

Hi, I'd like to know which functions in a package call one specific function. I think I've seen a tool for identifying such dependencies, but now I can't find it :-( Searches of help and R site search for keywords like function, call, tree, depend haven't helped :-( Can anyone point me in the right direction? Thanks in advance, Keith Jewell

Hello, pointed to the article "Debugging Without (Too Many) Tears" of Mark Bravington in Rnews Vol 3/3, December 2003 there is a package mvbutils mentioned. So I started to install this package from within R > install.package(mvbutils) I receive an error essage that this package is not found! Is due to a merge,removal or rename of this package? When I try to follow this

Hello R devel/help, I ran into this strange behavior: # showstack is supposed to walk through the stack of parent # environments when it is called: showstack = function() { env = environment() for(i in 1:12) { env = do.call(parent.frame, list(), env=env) print(env) } } # a simple chain of functions: g3=function(t) showstack()

Hello R devel/help, I ran into this strange behavior: # showstack is supposed to walk through the stack of parent # environments when it is called: showstack = function() { env = environment() for(i in 1:12) { env = do.call(parent.frame, list(), env=env) print(env) } } # a simple chain of functions: g3=function(t) showstack()

I've had repeated problems with promptClass missing methods, usually telling me a class has no methods when it does. In my current case, I've defined an S4 class "mspathCoefficients" with a print method setMethod("print", signature(x="mspathCoefficients"), function(x, ...) { # etc The file promptClass creates has no methods in it. >

I would like to follow up on another one of the documentation issues raised in the discussion on function hints. Duncan mentioned that the R core were working on preprocessing directives for .Rd files, which could possibly include some sort of include directive. I was wondering if a "includeexamples" directive might also be considered. It often makes sense to use the same example to

Is it possible to replace the word "R Console" on the title bar (is it what it's called? It's the blue area above menu bar) with the name of the work space file you're using or loaded, so people who are runing multple R sessions at same time can identify them immediately. I'm using 1.9.0 in SDI mode. Thanks, ...Tao