similar to: number of parameters of a function.

I didn't see any mention of this in the material on CRAN. The two S.h files define R_problem_buf as a real symbol rather than simply declaring its existence. As a result, a shared library that links two or more files that include this will get duplicate symbol complaints. Since it is not defined elsewhere in the code, someone has to define it. A secondly thing is the documentation for .C()

We have finally configured the R-Java interface as a `regular' R package. This allows R users to create arbitrary Java objects and call any accessible method. It has a reasonably sophisticated mechanism for handling transferring of arguments from R to Java and vice-versa, and allows Java classes to be implemented via R functions. The package and all the documentation is available from

> From: "Yves Gauvreau" <cyg at sympatico.ca> > References: <Pine.GSO.4.05.10006170711230.12526-100000 at auk.stats> > Date: Sat, 17 Jun 2000 08:41:57 -0400 > Sender: owner-r-help at stat.math.ethz.ch > Precedence: bulk > > This discussion is quite interesting. From the little I know of these issues > may I humbly suggest that parallelism may be the

Hello, JIT compiler interferes with internal R completions: compiler::enableJIT(2) utils:::functionArgs("density", '') gives: utils:::functionArgs("density", '') Note: no visible global function definition for 'bw.nrd0' Note: no visible global function definition for 'bw.nrd' Note: no visible global function definition for 'bw.ucv'

I initially sent this to the biocore mailing list - but it was suggested that r-devel would also find it interesting. Many of us use a macro like #define CALL_DEF(fname, nargs) { #fname, (DL_FUNC)&fname, nargs} for use in function registration for use with .Call. For example, using the example from R Extension manual, if we want to register a C function myCall with three arguments, we

I'm still getting used to R's scoping. I've run into the following situation value=0 thefunction <- function() print( value ) somefunction <- function() { value=99; thefunction() } somefunction() now, I understand that somefunction() returns 0 because thefunction() was defined with value=0 in its parent envrionment, it dosent look at all in the environment of somefunction. My

Just a note to complete this thread regarding the RSPython package. A binary version for this package is now available for Windows, compiled against R-1.4.0 and Python 2.2. Also makefiles and instructions are provided for compiling it oneself. It currently works only for one direction, namely embedding Python within R. As time permits, I'll add the embedding of R in Python to make it the same

I have finally got around to putting 4 packages on the Omegahat web site for use on Microsoft Windows. The packages are: RDCOMClient - interactive, dynamic access to arbitrary (D)COM objects from within R that allows one to create COM objects from R and call their methods and access their properties without the need to compile any code specific to the COM object. RDCOMServer - facility for

markus.jantti@iki.fi wrote: > > Full_Name: Markus Jantti > Version: 1.5.1 > OS: GNU/Linux Unstable (Sid) > Submission from: (NULL) (193.166.59.44) > > I was trying to get the package yags 3.20 by Vince Carey > <stvjc@channing.harvard.edu> > to run, but - after successfull installation -- loading the library failed with > the > message > > >

Thanks for your help Duncan. Your last comment helped me to figure out what FreeBSD was doing differently than Linux/Solaris. This fix worked on a machine with Python 2.1, R 1.3.1 and FreeBSD 4.1. Here are the details: The pthreads fix: I added '-lc_r' to the PKG_LIBS definition in src/Makevars.in. The FreeBSD 'man pthread' page suggests that adding -pthread to the gcc statement

I am writing a function to work with class I am defining. I have a question about using nargs() inside of parentheses function. nargs() shows the same for supplying 1 argument, or no arguments at all. Here is a small example: > "[.myclass"<-function(x,...) print(nargs()-1) > x<-c(1,2,3) > class(x)<-"myclass" > x[] [1] 1 > x[1] [1] 1 > x[1,2] [1] 2

I am new to llvm so I might be missing a critical step. My system is Fedora 12 but this also happens in Mac OS X 10.6.2. Here are the steps I used to compile llvm: export TARGETS=x86,x86_64,cpp export INSTALLDIR=/home/rovitotv/llvm ../llvm-2.6/configure --prefix=$INSTALLDIR --enable-bindings=none --enable-targets=$TARGETS --enable-optimized --with-llvmgccdir=$INSTALLDIR

First, you have to call llvm-g++ to use the llvm-gcc front end, but it doesn't matter here. I'd like to suggest that you use pastebin to put your code and the send us the link, so that we can download it. The problem is that TheExecutionEngine is set to NULL (maybe because of a previous error), but it will be really better if you use pastebin. On Wed, Feb 17, 2010 at 6:01 AM, Todd Rovito

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I know there is a function - I have used it before - but I always forget what it is called... I need the combination of two character vectors, i.e: x <- c("a", "b") y <- c("x", "y") z <- THEFUNCTION(x, y) z == c("ax", "ay", "bx", "by") I promise I will

(1) It seems to me that, generally, in R it is not possible to overload functions. Is that right? (2) Assuming that the above is true, or partially true, is there any extra packages to handle overloading in R? (3) Assuming (1) is TRUE and (2) is FALSE, can anyone provide some advice on developing some function that understand what the arguments are and then calls the right overloaded

(Sorry for the cross-post--- I wasn't sure which list is more appropriate...) Hi everyone, I've run into segfaults when using my randomForest package on large dataset (e.g., 100 x 15200) and large number of trees (e.g., ntree=7000 and mtry=3000). I'm wondering if anyone can give me some hints on where to look for the problem. The randomForest package mainly consists of two things:

(Sorry for the cross-post--- I wasn't sure which list is more appropriate...) Hi everyone, I've run into segfaults when using my randomForest package on large dataset (e.g., 100 x 15200) and large number of trees (e.g., ntree=7000 and mtry=3000). I'm wondering if anyone can give me some hints on where to look for the problem. The randomForest package mainly consists of two things:

Hi Stefan, Thank you very much for answering my question! I followed your suggestion but the function still cannot return the correct result. I also set target-feature attributes for my function. I am using LLVM 6.0. It only prints out some random large numbers but the correct answer is supposed to be all 0. Can you please help me figure out what's going on here? Any help will be greatly

In R's sprintf() if any of the arguments has length 0 the function aborts. E.g., > sprintf("%d", integer(0)) Error in sprintf("%d", integer(0)) : zero-length argument > sprintf(character(), integer(0)) Error in sprintf(character(), integer(0)) : 'fmt' is not a non-empty character vector This comes up in code like x[nchar(x)==0] <-

Dear all, I am using LLVM C++ API to generate some code. In particular, I am dealing with AVX2 SIMD API which uses __m256i. My function input types a set of vectors and return type is also a vector. /////////////////////////////////////////////////////////////////////////////////////////// arguments.push_back(VectorType::get(IntegerType::getIntNTy(TheContext, 64), 4));//int64*4 = __m256i