search for: call_s

Just out of curiosity, here is a question that might be embarrasingly stupid. Hmm ... What I need is to call runif() (more precisely, `runif(1, 0, 1)') from inside a C function. Is this possible using call_S? If so, how? -k =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-dev...

Hi Suman, I think you can ascertain pureness automatically leveraging the compiler instead of manually tagging attribute to each method and call-site. It would seem like impurity should be a transitive attribute. So this would conflict with below. __attribute__((annotate("pure"))) int add(uint32_t a, uint32_t b) { // impure by calling printf... ... printf("%d + %d =

...b90 edi=80000000 # eip=004d2a04 esp=0022c840 ebp=0022c868 iopl=0 nv up ei pl nz na po nc # cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206 # # Call stack: # 004D2A04 R.dll:004D2A04 malloc # 0054FEFA R.dll:0054FEFA Rf_allocVector # 0051AA10 R.dll:0051AA10 call_S # 0051ABB7 R.dll:0051ABB7 call_S # 0051AF18 R.dll:0051AF18 do_int_unzip # 00559594 R.dll:00559594 do_internal # 0052A3C8 R.dll:0052A3C8 Rf_eval # 0052BA52 R.dll:0052BA52 do_begin # 0052A3C8 R.dll:0052A3C8 Rf_eval # 0052A3C8 R.dll:0052A3C8 Rf_eval # 0052BA52 R.dll:0052BA52 do_begin #...

Consider the following simple C program: /*** hello_r.c ***/ #include <Rinternals.h> SEXP hello() { return mkString("Hello, world!\n"); } int main(void) { SEXP x = hello(); return x == NULL; /* i.e. 0 on success */ } This program segfaults: % myR/bin/R CMD LINK gcc -I./R-2.9.0/src/include -L./myR/lib64/R/lib -lR hello_r.c -o hello_r > /dev/null % hello_r zsh:

On Wed, Oct 25, 2017 at 11:33:43AM +0200, Juergen Gross wrote: > On 04/10/17 17:58, Josh Poimboeuf wrote: > > Some of the paravirt '*_CLOBBERS' macros refer to output constraints > > instead of clobbers, which makes the code extra confusing. Rename the > > output constraint related macros to '*_OUTPUTS'. > > > > Signed-off-by: Josh Poimboeuf

On Wed, Oct 25, 2017 at 11:33:43AM +0200, Juergen Gross wrote: > On 04/10/17 17:58, Josh Poimboeuf wrote: > > Some of the paravirt '*_CLOBBERS' macros refer to output constraints > > instead of clobbers, which makes the code extra confusing. Rename the > > output constraint related macros to '*_OUTPUTS'. > > > > Signed-off-by: Josh Poimboeuf

...all of Yellowstone National Park, on the order of 20 million pixels). Has anyone come up with a reasonable method to process big datasets using predict.rpart? I've been experimenting with a C program that sequentially calls predict.rpart to process smaller subsets of a large dataset using the call_S() Splus function, but it's really slow. I would appreciate any suggestions. Regards, Chris Wright p.s. I would like to subscribe to the r-help list -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~horni...

...b90 edi=80000000 # eip=004d2a04 esp=0022c840 ebp=0022c868 iopl=0 nv up ei pl nz na po nc # cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206 # # Call stack: # 004D2A04 R.dll:004D2A04 malloc # 0054FEFA R.dll:0054FEFA Rf_allocVector # 0051AA10 R.dll:0051AA10 call_S # 0051ABB7 R.dll:0051ABB7 call_S # 0051AF18 R.dll:0051AF18 do_int_unzip # 00559594 R.dll:00559594 do_internal # 0052A3C8 R.dll:0052A3C8 Rf_eval # 0052BA52 R.dll:0052BA52 do_begin # 0052A3C8 R.dll:0052A3C8 Rf_eval # 0052A3C8 R.dll:0052A3C8 Rf_eval # 0052BA52 R.dll:0052BA52 do_begin #...

...b90 edi=80000000 # eip=004d2a04 esp=0022c840 ebp=0022c868 iopl=0 nv up ei pl nz na po nc # cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206 # # Call stack: # 004D2A04 R.dll:004D2A04 malloc # 0054FEFA R.dll:0054FEFA Rf_allocVector # 0051AA10 R.dll:0051AA10 call_S # 0051ABB7 R.dll:0051ABB7 call_S # 0051AF18 R.dll:0051AF18 do_int_unzip # 00559594 R.dll:00559594 do_internal # 0052A3C8 R.dll:0052A3C8 Rf_eval # 0052BA52 R.dll:0052BA52 do_begin # 0052A3C8 R.dll:0052A3C8 Rf_eval # 0052A3C8 R.dll:0052A3C8 Rf_eval # 0052BA52 R.dll:0052BA52 do_begin #...

Martin, You are making your life way too complicated. There are a number of things I would do differently: 0) Wrong list. Rcpp has its down, rcpp-devel, and I basically do not read this and would have missed this were it not for luck. On 3 December 2017 at 02:06, Martin M?ller Skarbiniks Pedersen wrote: | I have read some web-pages about Rcpp and C++ but it is a bit confusion | for me. 1)

Luben, We all have different types of learning and how we approach this, let alone how we decompose things. With that, sorry you found this frustrating. Many of us put volunteer time into this trying to make things 'possible' and preferably 'easy' but we don't always get there. That said, I have shown multiple times over the last few years that the simple _one statement

Hello, I am trying to use Rinside package in my VC++.Net program ( using Visual Studio 8.0 environment). I have downloaded Windows binary of RInside from the following link http://cran.r-project.org/web/packages/RInside/index.htm Version of RInside - 0.2.3 While compiling the program , i am getting about 69 error. Some of them are the folllowing ones. Please me in solving the following issue

Hello folks, I'm not a compiler expert or subscribed to this mailing list, but I have a unique problem. I need to split a large piece of C/C++ code into two separate libraries: one library that only has pure code (i.e., code that doesn't require operating system interactions) and other library that can have both pure code and side-effecting code. I was was wondering if it's possible

On 04/10/17 17:58, Josh Poimboeuf wrote: > Some of the paravirt '*_CLOBBERS' macros refer to output constraints > instead of clobbers, which makes the code extra confusing. Rename the > output constraint related macros to '*_OUTPUTS'. > > Signed-off-by: Josh Poimboeuf <jpoimboe at redhat.com> I'm fine with the changes, but you might want to rename the

...t belonged to). Anyway, there is a workaround to call R functions from FORTRAN which is used in the "integrate" library. It was invented for S by Mike Meyer. The FORTRAN code needs to be written to call a fixed C function and pass it a pointer to the R function. The C function then uses call_S to call the R function. As everything is passed by reference in FORTRAN the argument is automatically a pointer. Since the FORTRAN code never does anything with the pointer except pass it, you can declare the argument to have any type you like. "integrate" declares the function pointer...

Hi Is there a way to call R-Functions from C directly ? Is there an API Any comments are welcome. Thanks Reinhard -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To:

...(is that possible or is it necessary to return at least a dummy?). This is from the example and func takes one double and returns one: void *args[1]; char *mode[1], *values[1]; long length[1]; double zz[1], *result; mode[0] = "double"; length[0] = 1; args[0] = (void*)(zz); zz[0] = z; call_S(func, 1L, args, mode, length, 0L, 1L, values); Thanks for the help Adrian -- Adrian Trapletti, Vienna University of Economics and Business Administration, Augasse 2-6, A-1090 Vienna, Austria Phone: ++43 1 31336 4561, Fax: ++43 1 31336 708, Email: adrian.trapletti at wu-wien.ac.at -.-.-.-.-.-....

Hi, I have written a small C++ function and compile it. However in R I can't see the function I have defined in C++. I have read some web-pages about Rcpp and C++ but it is a bit confusion for me. Anyway, This is the C++-code: #include <Rcpp.h> using namespace Rcpp; // [[Rcpp::export]] List compute_values_cpp(int totalPoints = 1e5, double angle_increment = 0.01, int radius =

On 3 December 2017 at 20:19, Dirk Eddelbuettel <edd at debian.org> wrote: Hi Dirk, Thanks for your answers. I got a few more questions. > > 0) Wrong list. Rcpp has its down, rcpp-devel, and I basically do not read > this and would have missed this were it not for luck. OK. I did found the rcpp-devel mailing-list. But I though it was a developers of the rcpp-package. So it is ok

Some of the paravirt '*_CLOBBERS' macros refer to output constraints instead of clobbers, which makes the code extra confusing. Rename the output constraint related macros to '*_OUTPUTS'. Signed-off-by: Josh Poimboeuf <jpoimboe at redhat.com> --- arch/x86/include/asm/paravirt_types.h | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff