similar to: new bug in install.packages()

Hi, When 'x' is a vector of doubles, it's not clear how 'factor(x)' compares its values in order to determine the levels. For example, here all the values in 'x' are "conceptually" the same: x <- c(11/3, 2/3 + 4/3 + 5/3, 50 + 11/3 - 50, 7.00001 - 1000003/300000) However, due to machine rounding errors, they are not

I've just had the error below while trying to install a package from source under R2.2.1 and Windows XP. I recall encountering this sporadically in the past. It is a pretty confusing message and took me quite some time to figure out; I've seen queries about it on the R site search, but couldn't find a reply. There's an attempted diagnosis and suggested cure below.

Dear list Can anyone suggest a simple way to abort execution like stop(...) does, but without issuing an "Error: ..." message? I don't want to set 'options( show.error.messages=TRUE)' because I want normal behaviour to resume after this particular stop. (Please reply personally as well as to the list, as I'm not subscribed to R-help) Thanks Mark -- Mark Bravington

R can run external code in C, C++, Fortran, Delphi, etc., but the R extensions manual only gives limited documentation for anything but C and C++. It would be useful to have a collection of sample code showing how to dyn.load functions written in other languages, if necessary for a variety of different compilers, in case that makes a difference. Does such a collection already exist? If not,

There is a bug in `predict' whereby the order of variables sometimes gets re-arranged compared to the original fit, and then disaster results. Specifically, the 'variables' and 'predvars' attributes of a 'terms' object get out of synch. This only happens when the terms in the original formula get re-ordered during fitting: test> scrunge.data_ data.frame(

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]

Several times my packages have fallen foul of the latex check at the uploading-to-CRAN stage, creating extra work for Kurt Hornik. I've never bothered trying to get latex working on my own packages (happy with vanilla help) but am told that "latex is the closest thing to a syntax checker for Rd files" and that I should set it up. Now, there is already a latex on my (Windows XP)

Dear R-devel On my Windows 2000 machine, I can build R-patched but not R-devel (since at least 1/9/2004). An error message pops up during the execution of some R code during "make", as below. In terms of "make" etc., I am totally clueless (not being a user of either Linux or C) and just mechanically follow the instructions in the R documentation; hence I've got no idea

Hi, The cleanup_pkg() function defined the big tools:::.build_packages() function in tools/R/build.R is currently broken. When Makefiles are used cleanup_pkg() doesn't clean anything because of the way system2() is called. For example, the call to Ssystem() on line 304 (Ssystem is a silent version of system2) is basically trying to do this: >

Hi! I have renamed some functions and deleted others. I have noticed that R CMD check complains only about newly added functions, but documented non-anymore-existing functions seem not to matter. I knew about prompt and promptMethods promptClass. They are extremely useful if you are starting to write a package. But what with existing packages that have to be rewritten? Having code and

Is there a way to rename a function when importing it? I want to say, "import yourFunc from Foo as myFunc" in the NAMESPACE file. Does this exist and I've missed it? If it doesn't exist, would others think it useful (and possible)? Best, + seth

Problem below with PCRE grep in R-devel; works fine in R-patched. (Unless there's been an absolutely massive change in rules for updated PCRE version 8.13; jeez I hope not) > grep( '[.][.]', '', perl=TRUE) Error in grep("[.][.]", "", perl = TRUE) : invalid regular expression '[.][.]' In addition: Warning message: In grep("[.][.]",

'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(

A bit late for Santa, but on my wish-list nevertheless: is there any chance that "scan" and "readLines" could be extended to take a parameter "until" or "EOF.marker", which would be a character string that (if encountered while reading) would cause the reading to stop, just as if an end-of-file had been found? [But leaving a connection open, so that

# 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),

I'm encountering excruciatingly slow load times for character vectors in R 2.6.0-- up to 30sec for a 15K file that contains a no-attributes character vector of length ~1e4 and object size ~0.5MB. In R 2.5.1, repeated loads of the same set of files are near-instantaneous. The problem is proving tricky to reproduce consistently from scratch, so I have attached the 3 files used in the examples

Hi, According to its man page substring() "expands (its) arguments cyclically to the length of the longest _provided_ none are of zero length". So, as expected, I get an error here: > substring("abcd", first=2L, last=integer(0)) Error in substring("abcd", first = 2L, last = integer(0)) : invalid substring argument(s) But I don't get one here:

Hi, Today we've seen the following problem with the R-2.12 that we use for our Windows builds: > installed.packages() Error: subscript out of bounds After some investigation we discovered that the cause of this failure was that 1 of the 890 packages currently installed on the machine (Windows Server 2003 R2) had its DESCRIPTION file empty:

Hi, The following code produces different kinds of problems depending on which platform you run it: x <- as.list(1:200000) names(x) <- paste("A", 1:200000, sep="") e <- list2env(x) Timeout on Linux, crash on Mac and Windows, with R 2.12.0 and current R devel. The "multi-assign" mode (i.e. when the 'envir' arg is supplied) doesn't seem

I get this (with R-2.12 and R-2.13, didn't try with earlier versions): > max(c(NaN, NA)) [1] NA > max(c(NA, NaN)) [1] NaN I get the same thing with min(). The fact that the result of 'max(x)' or 'min(x)' depends on the order of the elements in 'x' is surprising. It also seems to contradict the man page: By definition the min/max of a numeric vector