Inspired by
http://stackoverflow.com/questions/7487778/could-you-tell-me-what-this-error-means
I wrote the following very small (one-line) patch which returns an
*informative* error message when R tries to load a zero-byte file rather
than
Error in if (!grepl("RD[AX]2\n", magic)) { : argument i
On 11-09-20 09:29 PM, peter dalgaard wrote:
>
> On Sep 20, 2011, at 20:57 , Ben Bolker wrote:
>
>>
>> From SVN revision 57032, with configuration
>>
>> R is now configured for i686-pc-linux-gnu
>>
>> Source directory: . Installation directory:/usr/local
>>
>> C compiler:
On Sep 20, 2011, at 20:57 , Ben Bolker wrote:
>
> From SVN revision 57032, with configuration
>
> R is now configured for i686-pc-linux-gnu
>
> Source directory: .
> Installation directory:/usr/local
>
> C compiler:gcc -std=gnu99 -g -O2
> Fortran 77 compiler
From SVN revision 57032, with configuration
R is now configured for i686-pc-linux-gnu
Source directory: .
Installation directory:/usr/local
C compiler:gcc -std=gnu99 -g -O2
Fortran 77 compiler: gfortran -g -O2
C++ compiler: g++ -g
On 20 September 2011 at 10:26, Alireza Mahani wrote:
| I have a function in R that takes another function as argument:
|
| f <- function(g, ...) { #g is expected to be a function
| }
|
| I want to see if there is a way to implement "f" in C and calling it from R
| using ".C" interface. I know th
You can't call "R" code as if it is C code. It is R, and requires
that it be evaluated. How would your C know what to do with an R
pointer...
.Call is more efficient than .C, all the time. Check this list and
experiment. That said, you can still call "just C" within the .Call
"R" function, it
OK, thanks. But there are two issues with using ".Call":
1- I may give up performance if I am literally running R code inside C,
right? In some ways, wouldn't it defy the purpose of calling a compiled code
if I end up back in R?
2- If I use the ".Call" interface, the resulting code will be tailor
2011/9/20 Uwe Ligges
> You can evaluate R functions from C, see Writing R Extension.
>
Yes, I think they create a baby lapply function implemented in C (Which
obviously involves evaluating a function).
Also, just fyi, you want the .Call interface, not the .C interface.
~G
>
> Uwe Ligges
>
>
You can evaluate R functions from C, see Writing R Extension.
Uwe Ligges
On 20.09.2011 19:26, Alireza Mahani wrote:
I have a function in R that takes another function as argument:
f<- function(g, ...) { #g is expected to be a function
}
I want to see if there is a way to implement "f" in C a
I have a function in R that takes another function as argument:
f <- function(g, ...) { #g is expected to be a function
}
I want to see if there is a way to implement "f" in C and calling it from R
using ".C" interface. I know that I can use function pointers for my C
implementation, but I imagin
Hi everyone,
I use the boot package within the MBESS package to automate much of
the hard part for folks interested in performing a (simple) mediation
model. The function mediation() works well, except for a (probably)
unrealistic artificial data set.
When I apply the bootstrap I sometimes get:
E
Other than the RServe part, I do this all the time. It works well. Perhaps we
can put together some notes off-line and then bring it back to the list.
Paul
> -Original Message-
> From: r-devel-boun...@r-project.org [mailto:r-devel-bounces@r-
> project.org] On Behalf Of Cook, Malcolm
> Se
12 matches
Mail list logo
