similar to: anyway to get R unevaluated expr independent on arguments

Sometimes I get confused with R's documentation. It seems the documents is not maintained and updated well. Anyone has similar feeling? I don't mean to offend anyone. I hope R would get better and better. But documentation is really one very important factor which could attract people coming or drive people away. Xin Zheng [[alternative HTML version deleted]]

Hi all, Is there any way to keep numeric colnames as is? Any hint will be appreicated. Xin Zheng [[alternative HTML version deleted]]

Hi there, I got a data frame with more than 200k columns. How could I get median of each column fast? mapply is the fastest function I know for that, it's not yet satisfied though. It seems function "median" in R calculates median by "sort" and "mean". I am wondering if there is another function with better algorithm. Any hint? Thanks, Xin Zheng

Le lun. 9 d?c. 2019 ? 09:57, Tomas Kalibera <tomas.kalibera at gmail.com> a ?crit : > On 12/9/19 2:54 PM, Laurent Gautier wrote: > > > > Le lun. 9 d?c. 2019 ? 05:43, Tomas Kalibera <tomas.kalibera at gmail.com> a > ?crit : > >> On 12/7/19 10:32 PM, Laurent Gautier wrote: >> >> Thanks for the quick response Tomas. >> >> The same error

Hi Simon, Widespread errors would have caught my earlier as the way that code is using only one initialization of the embedded R, is used quite a bit, and is covered by quite a few unit tests. This is the only situation I am aware of in which an error occurs. What is a "correct context", or initial context, the code should from ? Searching for "context" in the R-exts manual

Dear R developers, just a quick question: I noted that R_ParseVector () has gained an additional parameter (since SVN rev. 39999). Since R_ParseVector () is part of the public API, I'm wondering, whether this API change was intentional or not. Either way is fine with me, but in order to make sure the next release of RKWard will be compilable with R 2.5.0, I'd like to make sure,

Le lun. 9 d?c. 2019 ? 05:43, Tomas Kalibera <tomas.kalibera at gmail.com> a ?crit : > On 12/7/19 10:32 PM, Laurent Gautier wrote: > > Thanks for the quick response Tomas. > > The same error is indeed happening when trying to have a zero-length > variable name in an environment. The surprising bit is then "why is this > happening during parsing" (that is why

Dear List, When I try to parse code containing newline characters with R_ParseVector, I get a compilation error. How can I compile code that includes comments and newlines? I am using the following: void* my_compile(char *code) { SEXP cmdSexp, cmdExpr = R_NilValue; ParseStatus status; PROTECT (cmdSexp = allocVector (STRSXP, 1)); SET_STRING_ELT (cmdSexp, 0, mkChar (code));

In src/main/gram.y, the documentation for R_ParseVector has a wrong signature: SEXP R_ParseVector(TextBuffer *text, int n, ParseStatus *status) should be SEXP R_ParseVector(SEXP text, int n, ParseStatus *status) In addition, the two occurrences of "IOBuffer" in the documentation should be replaced by "IoBuffer". version.string = Version 2.3.0 beta (2006-04-14 r37779)

Thanks for the quick response Tomas. The same error is indeed happening when trying to have a zero-length variable name in an environment. The surprising bit is then "why is this happening during parsing" (that is why are variables assigned to an environment) ? We are otherwise aware that the error is not occurring in the R console, but can be traced to a call to R_ParseVector() in

Hi r-devel, The R_ParseVector has been changed in R-2.5.0, and there is a simple description about the 4th argument at http://stat.ethz.ch/R-manual/R-patched/NEWS, it says that: "R_ParseVector() has a new 4th argument 'SEXP srcfile' allowing source references to be attached to the returned expression list. " I do not quite understand the purpose of adding the 4th argument. Would

Hi again, Beside R_ParseVector()'s possible inconsistent behavior, R's handling of zero-length named elements does not seem consistent either: ``` > lst <- list() > lst[[""]] <- 1 > names(lst) [1] "" > list("" = 1) Error: attempt to use zero-length variable name ``` Should the parser be made to accept as valid what is otherwise possible

Hello, [I'm redirecting this here from stats-rosuda-devel] When parsing R code through R_parseVector and the code generates an error (syntax error), is there a way to grab the error. It looks like yyerror populates the buffer "R_ParseErrorMsg", but then the variable is not part of the public api. Would it be possible to add yet another entry point to the parser that would

Hi, I think this is a bug (even though I can't find documentation explicitly saying that it should work). Basically, Rf_PrintValue(obj) fails when 'obj' is an S4 object that should be printed using show() rather than print(). From the error message I'm guessing that the need to use show is detected correctly but then show is not found. "cbind2" in the code below is just

Hi, Forum newb here, looking for some help. Have been trying to install an R-Java interface to make R calls from Java. JRI's configure script runs fine, but when it comes to make, I get the "error: too few arguments to function 'R_ParseVector'" Java runs fine. R runs fine. But I can't get this .jar file created. <grumble> Any help would be appreciated immensely,

Hi, The behavior of ``` SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); ``` defined in `src/include/R_ext/Parse.h` appears to be inconsistent depending on the string to be parsed. Trying to parse a string such as `"list(''=1+"` sets the `ParseStatus` to incomplete parsing error but trying to parse `"list(''=123"` will result in R sending a message to the

Hello, I've been using R embedded in PL/R (R procedural language handler for PostgreSQL, http://www.joeconway.com/plr/) very successfully for several months now. A sincere "thank you" goes to the R development team for such a great product. I have a question I'm hoping someone here can help me with. In order to get the required functionality out of PL/R, I've had to

Thanks to Deepayan Sarkar (lattice) and Paul Murrell (grid) I have nearly finished porting the Hmisc library's xYplot function to R. xYplot extends xyplot to allow for error bars, bands, and a few other features. In S-Plus I extended the Trellis function xyplot mainly by writing panel.xYplot. In R, xyplot contains a lot of code, so I implemented xYplot by calling xyplot from it. Things are

Folks: Herein is a suggestion for a little R convenience function mainly to obtain unevaluated ... function arguments. It arose from a query on R-help on how to get these arguments. The standard (I think) idiom to do this is via match.call(expand.dots=FALSE)$... However, Bill Dunlap pointed out that this repeats the argument matching of the function call and suggested a couple of alternatives

Dear all, my aim is to integrate R in an interactive visualisation software called Bulk Analyzer developed by VrVis (http://www.vrvis.at). the code: SEXP e, tmp; ParseStatus status; PROTECT(tmp = mkString("x <- c(1.234,-3.45)")); PrintValue(tmp); PROTECT(e = R_ParseVector(tmp, -1, &status, R_NilValue)); PrintValue(e); UNPROTECT(2); produces the following output: [1] "x