similar to: Multi-line string constants: proposal

> Kevin Wright <kwright@eskimo.com> writes: > > > R 1.9.1 requires multi-line strings to contain a backslash at the > > end of each line (except the last line). As noted by Mark > > Bravington (http://tolstoy.newcastle.edu.au/R/help/02b/5199.html) > > this requirement appears to be undocumented. > > > > In S-Plus 6.2, multi-line strings do

'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

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

Hmmm-- still looks like a bug to me! But as I don't want to hog the airwaves, here's my last summary on this point, with a question: [Bravington] #> Prediction from the original data was just an example, of course; my general #> proposal is that inactive factor levels in the prediction set should be #> dropped. I don't see how this could ever cause inconsistent behaviour

The function 'getAnywhere' crashes if given a non-existent name containing a period: > getAnywhere( 'nomethod.noclassforme') Error in get(x, envir, mode, inherits) : variable "nomethod" was not found However, 'getAnywhere' behaves gracefully if the non-existent name lacks a period: > getAnywhere( 'nomethod') no object named `nomethod' was

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>

Is this the last bug of the year? Well, it's the last one from me, anyway... The "parse" function seems to give erratic behaviour when used in conjunction with "pushBack" on an open connection (R1.6.1, Windows 2000). Try this: > { cat( c( '1', 'a+b', '2'), file='r123.r', sep='\n'); tcon_ file( 'r123.r'); open( tcon);

# r-bugs@r-project.org `termplot' bombs if the original dataset contains NAs in the predictors, even if these were ignored during fitting: test> bug.data_ data.frame( x=c(1:3, NA), y=runif( 4)) test> lm.tpbug_ lm( y~x, data=bug.data) test> termplot( lm.tpbug) Error in xy.coords(x, y, xlabel, ylabel, log) : subscript out of bounds A simple fix seems to be add the

When replacing all elements of a column in a data.frame, a corrupt data.frame will be generated if the replacer is "short": test> bbb <- data.frame( x=1:2) test> bbb[,'x'] <- 3 # should fill the column test> bbb x 1 3 2 <NA> Warning message: corrupt data frame: columns will be truncated or padded with NAs in: format.data.frame(x, digits = digits)

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

#-----Original Message----- #From: Duncan Murdoch [mailto:dmurdoch@pair.com] #I forget whether Erich mentioned it in this post, but in other #messages he's told me that the intention is to use this as a way to #start R for naive users, immediately firing up Rcmdr for instance. #It's possible to install a .First function for such users, but it #would be easier if the capability was built

When something gets printed by the "print.default" function, any extra attributes are printed without regard to their class attribute (if any). For example: > x <- 1:3 > attr( x, 'other') <- factor( c( 'cat', 'dog')) > attr( x, 'other') [1] cat dog Levels: cat dog > x [1] 1 2 3 attr(,"other") [1] 1 2 which is perhaps

You might want to have a look at 'source.mvb' & friends in the 'mvbutils' package. It's designed to allow control of nested sourcing, and to allow interspersed data and commands in a single self-contained file. Unlike 'source', 'source.mvb' reads each statement and immediately executes it, before proceeding to the next; hence it has do the parsing to figure

In R-1.7.1, I used to be able to append a character vector to a 'tklistbox' with e.g. listio <- tklistbox( tktoplevel(), font='Courier', height=20, width=20, setgrid=TRUE) tkinsert( listio, 'end', letters[1:3]) tkpack( listio,side='left', expand=TRUE, fill='both') and three items would be added to 'listio'. This doesn't work in R-devel-- it

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

This is a question about namespaces and assignment. It's occasioned because one of my functions stopped working at about R1.6 with the arrival of 'namespace:base', and I'm anxious to find out what will happen when 1.7 arrives. But the question might be of more general relevance (hence my desire to get it in before "lockdown" on 9th April). I have a function

Dear newsgroup, There was a recent post suggesting the incorporation of a standard rmultinom(...). This seems like a good idea, but I wasn't sure about basing this on tabulate( sample( ...)). Despite the attractive succinctness, this could be very slow and use lots of memory if n or size is large. Instead, I've tended to use a loop over the boxes of the multinomial, taking successive

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

My reading of the R documentation is that the nature of the subscript i in x[[i]] is not specified; the only obvious rule is that it should lead to to a single element. Which is what I'm after: a way of extracting or changing the 4th element of the 2nd element of a list. Incidentally, the operational difficulty comes in general programming when I don't know in advance how many levels down