similar to: Seemingly bizarre behavior in R CMD check

Hi, This is (presumably?) a bug in R 1.7.0 under Windows. I have not tested it on other systems. Attachment of packages is case sensitive but not library(), resulting in multiple loadings of the same package if the library name is spelled differently. The following example loads the `tools' package, once as `tools' and once as `Tools'. This behavior is the same with all packages and

Hello, I am a new R user not at ease with installing and updating R package under Ubuntu (Hardy), so that I cannot run R anymore ...! I initially installed r version 2.6.2.2 (amd64) from Intrepid instead of Hardy (!), but it worked. I tried to update to version 2.9, but did not succeeded:    (1) I added to my /etc/apt/sources.list an entry :           deb

An update of the VR bundle was released on Monday and should have propagated around CRAN now. It is a collection of bug fixes (many to documentation, thanks to Kurt Hornik's great tools undoc and codoc) and small enhancements for R. It does need R 1.2.2 to install (the help files make use of new markup for methods) but only 1.2.0 to run. Thus the precompiled Windows version will run on

An update of the VR bundle was released on Monday and should have propagated around CRAN now. It is a collection of bug fixes (many to documentation, thanks to Kurt Hornik's great tools undoc and codoc) and small enhancements for R. It does need R 1.2.2 to install (the help files make use of new markup for methods) but only 1.2.0 to run. Thus the precompiled Windows version will run on

Hi, I would like to get a hint on how to debug in the case of #> R CMD check pllib signalling * checking for code/documentation mismatches ... WARNING Error in parse(file, n, text, prompt) : syntax error on line 22 I am able to sort out which of the files is the culprit is by swapping files in and out of the /R and /man directories. But I cannot find the syntax error, the .Rd file seems

As cool and wonderful as the package checking tools for R are, I sometimes am stymied when trying to track down a problem. For example, I occasionally see error messages when running R CMD check like the following: [...] * checking Rd files ... OK * checking for undocumented objects ... ERROR * in parse(file, n, text, prompt) : syntax error on line 932 * in undoc(dir =

Full_Name: Laurent Version: R-2.0.0-beta-from-a-week-ago OS: linux Submission from: (NULL) (202.156.6.77) When running 'R CMD check' for a package that contains the symbol '%' in the signature of a function (say the default parameter for a string argument is like "10% - 20%"), the 'codoc' part of the check throws a warning about mismatching doc and codoc. While

Dear R-devel, Can anyone help me to understand this? It seems that subscripting the rows of a data.frame without actually changing their order, somehow changes an internal representation of row.names that is revealed by e.g. dput/dump/serialize I have read the docs and inspected the (R) code for data.frame, rownames, row.names and dput without enlightenment. df=data.frame(a=1:10, b=1)

Hi, since nobody answered to my first message, I try to explain my problem more clearly and more general this time: I have a data set in my R package "micEcon", which has many variables (82). Therefore, I would like to avoid to describe all variables in the "\format" section of the documentation (.Rd file). However, doing this lets "R CMD check" complain about

Dear List: I'm posting this to provide a possible solution and to document to what appears to be an R limitation. The solution is more of a cheap hack that works for now. To provide a little background, I am looping through a dataframe and creating Sweave documents using data from each row in the dataframe. It appears that this technique is not scalable to large dataframes without making some

What is the Rd file alias and usage syntax for an S4 assignment method? I have been trying variations on \alias{TSdoc<-,default-method} \usage{ \S4method{TSdoc}{default}(x) <- value but so far I have not got it right according to various codoc, etc, checks. Paul Gilbert ==================================================================================== La version fran?aise

I have a function: source_dir <- function(path, pattern = "\\.[rR]$", chdir = TRUE) ... documented with ... \usage{source_dir(path, pattern="\\.[rR]$", chdir=TRUE)} ... But I get Codoc mismatches from documentation object 'source_dir': source_dir Code: function(path, pattern = "\\.[rR]$", chdir = TRUE) Docs: function(path, pattern =

Hi, Doing 'R CMD check diveMove' is now throwing this message: Data codoc mismatches from documentation object 'sealLocs': Variables in data frame 'sealLocs' Code: id.time.class.lon.lat Docs: class id lat lon time with: R> sessionInfo() R version 2.10.1 (2009-12-14) x86_64-pc-linux-gnu locale: [1] LC_CTYPE=en_CA.UTF-8 LC_NUMERIC=C

In revising the splancs package, I use R CMD check. After a number of changes to various files in the directory tree, R CMD check fails at the * checking for undocumented objects ... ERROR stage as shown below. But running undoc() in R (pointed at the Rcheck directory, not on the older version) doesn't show the same error, and grep on the Rcheck R code finds the function. I ran undoc() under

Hello, (Dear Richard, I hope you don't mind being Cc:'d on this thread in R-devel. This is one of the ways we can prevent similar problems from happening in the future.) Sometimes, package authors who use both exportPattern('.') and utils::globalVariables(...) get confusing WARNINGs about undocumented exports: https://stat.ethz.ch/pipermail/r-package-devel/2024q1/010531.html I

Temporary images can be quite big, more than the space available in $TMPDIR when it's on a tmpfs; hence, place them in our cachedir instead. --- builder/builder.ml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/builder/builder.ml b/builder/builder.ml index 957bc37..3750e5f 100644 --- a/builder/builder.ml +++ b/builder/builder.ml @@ -378,6 +378,8 @@ let main () =

>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>> on Mon, 27 Feb 2017 10:42:19 +0100 writes: >>>>> Rob J Hyndman <Rob.Hyndman at monash.edu> >>>>> on Wed, 15 Feb 2017 21:48:56 +1100 writes: >> The generic stats::median method is defined as median <- >> function (x, na.rm = FALSE)

Hi the list, I build a package. They was a mistake in it, but R CMD check did not find it. Is that normal ? Here is what Kurt gets (which is right, I did this mistake): --- 8< ---------------- * checking for code/documentation mismatches ... WARNING S4 class codoc mismatches from documentation object 'LongData-class': Slots for class 'LongData' Code: id other time traj

Hi, I'm trying to document a data frame in Rd format. The data frame contains a variable called 'Health_Env'. When I create a template for the Rd file using 'prompt()' the variable name is included as-is and when I run R CMD CHECK I get a latex error because latex considers '_' a special character (used for subscripts) which is only allowed in math mode. When I

Running R CMD check on a package can take quite a lot of time. Checks seem like they could be run in parallel (separate processes for, e.g., codoc, examples, tests, ...). Is there a way to do this? My current usage is typically R CMD build <pkg> R CMD check pkg_x.y.z.tar.gz Thanks for any hints, Martin -- Computational Biology Fred Hutchinson Cancer Research Center 1100