search for: call_

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-de...

...ll-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 = %d\n", a, b, c) __attribute__((annotate("call_ impure"))); Finding purity of functions should be possible by parsing each function across files and build up a call dag tree. You can traverse bottom-up to mark each function as impure from callees and using the definition of pure-ness. From there you could find two sets of functions, put th...

...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...

...ase, the main() function needs to do some initialization stuff on R before one can invoke functions like mkString(), but I have not been able to find what this initialization should be. If someone could point me in the right direction I'd appreciate it. Also, where is the documentation for the call_R function? It is mentioned several times in the Writing R Extensions document, but I have not been able to find the documentation for it. TIA! Kynn [[alternative HTML version deleted]]

...nstead 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 "call_clbr" > parameter of ____PVOP_[V]CALL, too, e.g. to "outputs". Yeah, good catch. > You could then drop the "CALL_" from the macros, too. Hm, which macros are you referring to, and why? -- Josh

...nstead 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 "call_clbr" > parameter of ____PVOP_[V]CALL, too, e.g. to "outputs". Yeah, good catch. > You could then drop the "CALL_" from the macros, too. Hm, which macros are you referring to, and why? -- Josh

...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/~horn...

...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...

...es) */ Then in R: R> library(Rcpp) R> sourceCpp("/tmp/mmsp.cpp") R> res <- compute_values_cpp() R> str(res) List of 2 $ x: num [1:100000] 199 362 118 302 262 ... $ y: num [1:100000] 20 40 14.3 39.5 36.9 ... R> _One call_ of sourceCpp() compiles AND links AND loads AND runs the example R code (which is optional). For reference, the current mmsp.cpp follows. Dirk #include <Rcpp.h> using namespace Rcpp; // [[Rcpp::export]] List compute_values_cpp(int totalPoints = 1e5, double angle_increment = 0.01, int rad...

...pose 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 call_ of `install.packages("tidyverse")` works in r2u as demonstrated in a Docker container for r2u. I just 'taped' a fresh demo installing 103 binary packages in twenty seconds from this one command. [1] Myself, and many others, take advantage of that day in, day out on Ubuntu systems...

...\Language.h 155 Qdev_R1 Error 318 error C2059: syntax error : '>' D:\R Lib\Packages\Rcpp\include\Rcpp\Language.h 164 Qdev_R1 Error 319 error C2143: syntax error : missing ';' before '{' D:\R Lib\Packages\Rcpp\include\Rcpp\Language.h 164 Qdev_R1 Error 320 error C2065: 'call_' : undeclared identifier D:\R Lib\Packages\Rcpp\include\Rcpp\Language.h 166 Qdev_R1 Error 321 error C3861: 'proxy': identifier not found D:\R Lib\Packages\Rcpp\include\Rcpp\Language.h 166 Qdev_R1 Error 322 error C2143: syntax error : missing ',' before '{' D:\R Lib\Packa...

...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 to achieve this by adding something like __attribute__((annotate("pure"))) and __attribute__((annotate("call_impure"))) and how much effort will it be to add such a functionality. Basically, I want "pure" attribute to be sticky, in the sense that every function that's pure, can only call pure code unless explicitly marked inside the function to make impure call. For example, the followin...

...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 "call_clbr" parameter of ____PVOP_[V]CALL, too, e.g. to "outputs". You could then drop the "CALL_" from the macros, too. Juergen

...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:

I would like to use the call_R mechanism. Unfortunately I don't fully understand what the arguments are from the example in "R-0.64.2/demos/dynload". Could anybody explain me how I have to define the arguments, e.g., I want to call R with 5 doubles (or double[5]) and func does not return a value (is that possible...

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 =

...uestions to rcpp-devel? > > 6) Call me crazy but maybe the nine vignettes included with the package? > OK. I will print them and read them. [...] > > Then in R: > > R> library(Rcpp) > R> sourceCpp("/tmp/mmsp.cpp") > > [...] > > _One call_ of sourceCpp() compiles AND links AND loads AND runs the example R > code (which is optional). Basically I was searching for ways to compile to C++ code a single time and not everything the R code runs. Like I don't recompile my pure C++ programs everything I run them, only if I change so...

...ions(-) diff --git a/arch/x86/include/asm/paravirt_types.h b/arch/x86/include/asm/paravirt_types.h index 0e112f279514..e99e5ac3e036 100644 --- a/arch/x86/include/asm/paravirt_types.h +++ b/arch/x86/include/asm/paravirt_types.h @@ -466,12 +466,12 @@ int paravirt_disable_iospace(void); #define PVOP_CALL_ARG2(x) "d" ((unsigned long)(x)) #define PVOP_CALL_ARG3(x) "c" ((unsigned long)(x)) -#define PVOP_VCALL_CLOBBERS "=a" (__eax), "=d" (__edx), \ +#define PVOP_VCALL_OUTPUTS "=a" (__eax), "=d" (__edx), \ "=c" (__ecx) -#d...