search for: matchargs

"sum" (and perhaps other functions?) allows partial argument name matching after its three-dots argument: > sum(1:4, NA, n=78, na.rm=FALSE) [1] 10 > sum(1:4, NA, n=78, na.rm=TRUE) [1] 11 I can see there could be a discussion about whether or not this is a bug, but I think all will agree that it's a might peculiar. This is done in 2.0.1 but the same behavior is in 1.8.1.

...erprimary.net/posts/2010/03/16/reentrant-bugs-without-concurrency/ http://userprimary.net/posts/2010/03/16/reentrant-bugs-without-concurrency/ identifies the error message formal argument "< >" matched by multiple actual arguments as a bug arising out of the R-internals function matchArgs Is there a work-around to this problem? I am using R version 2.12.2 (2011-02-25) Regards, Yashwanth -- View this message in context: http://r.789695.n4.nabble.com/Error-formal-argument-softmax-matched-by-multiple-actual-arguments-tp4260949p4260949.html Sent from the R help mailing list archiv...

Hello, Can anyone give me a pointer where to find the implementation code for binding values to formal arguments in functions? For example, if we have a function f <- function(x,y)... and f(1,2) is called, I want to find the code that binds 1 to x when evaluating f(1,2). I tried eval.c but it's too long and I was lost... Thanks! -- Yi

...char* to char* breaks something. I also don't know why const char* did not work. My bison is root@delta[src]# bison -V GNU Bison version 1.25 --- ./src/include/Rinternals.h.alpha-patch Sun Sep 12 17:41:57 1999 +++ ./src/include/Rinternals.h Sun Sep 12 17:43:37 1999 @@ -361,7 +361,7 @@ SEXP matchArgs(SEXP, SEXP); SEXP matchPar(char*, SEXP*); SEXP mkChar(const char*); -SEXP mkString(const char*); +SEXP mkString(char*); SEXP namesgets(SEXP, SEXP); int ncols(SEXP); int nrows(SEXP); --- ./src/main/gram.y.alpha-patch Tue Aug 10 10:56:17 1999 +++ ./src/main/gram.y Sun Sep 12 17:38:27 1999 @@ -56...

...gt; o subassignment x[[....]] <- y didn't check for a zero-length > right hand side, and inserted rubbish value. (PR#14217) > > o fisher.test() no longer gives a P-value *very* slightly > 1, > in some borderline cases. > > o Internal function matchArgs no longer modifies the general > purpose bits of the SEXPs that make up the formals list of R > functions. This fixes an invalid error message that would > occur when a garbage collection triggered a second call to > matchArgs for the same function via a fin...

...CTed too early (PR#14214) o subassignment x[[....]] <- y didn't check for a zero-length right hand side, and inserted rubbish value. (PR#14217) o fisher.test() no longer gives a P-value *very* slightly > 1, in some borderline cases. o Internal function matchArgs no longer modifies the general purpose bits of the SEXPs that make up the formals list of R functions. This fixes an invalid error message that would occur when a garbage collection triggered a second call to matchArgs for the same function via a finalizer. o...

...CTed too early (PR#14214) o subassignment x[[....]] <- y didn't check for a zero-length right hand side, and inserted rubbish value. (PR#14217) o fisher.test() no longer gives a P-value *very* slightly > 1, in some borderline cases. o Internal function matchArgs no longer modifies the general purpose bits of the SEXPs that make up the formals list of R functions. This fixes an invalid error message that would occur when a garbage collection triggered a second call to matchArgs for the same function via a finalizer. o...

I found a bug in one of the fourteen speed patches I posted, namely in patch-vec-subset. I've fixed this (I now see one does need to duplicate index vectors sometimes, though one can avoid it most of the time). I also split this patch in two, since it really has two different and independent parts. The patch-vec-subset patch now has only some straightforward (locally-checkable) speedups for