similar to: FW: Parsing multi-line strings. Bug? Feature?

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 not need a backslash for continuation. I recently (http://tolstoy.newcastle.edu.au/R/devel/04b/0256.html) requested

I have an S-Plus library that I would like to port to R. The library sends a mix of static and dynamic output to an html file. For example cat(" ... Big block of HTML formatting code ... ") cat(dat()) cat(" More static text ") With S-Plus I can just cut and paste HTML code from other files into my S-Plus script file. This makes maintenance of the script fairly easy. The

R's parser complains about syntax like this: a <- 'one string that covers several lines' The parser wants the first line to end with a backslash. Would it be possible to change the parsing rules to not require the backslash inside character strings? IE if the line ends before the string does, and the last character on the line isn't a [single] backslash, then just auto-add

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

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

'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

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

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

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

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

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

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

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

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

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

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

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

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);