similar to: calling an R-function from C

Hi, I sent the below message to r-devel but received no answer. I would like to contribute my system but I need som advice concerning the connections. Is my proposal of any interest to you? regards Ralf ?stermark ----- Forwarded message from Ralf ?stermark <rosterma at abo.fi> ----- Date: Mon, 21 Feb 2005 11:35:21 +0200 From: Ralf ?stermark <rosterma at abo.fi> Reply-To: Ralf

Hi, I would like to connect my GHA-system to R and to deliver the library to users of R. could you give me a comprehensive example containing the step by step procedure to: 1. create a callable library with R binaries (not having a standalone version of R with its own main()). If possible, I would like to run the system on unix,alpha,linux computers as well as on IBM's parallel

an ocfs-volume was nearly full (only 800MB free). i deleted some datafiles to free space: $ df -h . Filesystem Size Used Avail Use% Mounted on /dev/sdp1 10G 5.3G 4.8G 53% /db/DPS so there are more than 4GB available. $ sqlplus /nolog SQL*Plus: Release 9.2.0.4.0 - Production on Wed Sep 1 12:57:48 2004 Copyright (c) 1982, 2002, Oracle Corporation. All rights

On Tue, Sep 8, 2020 at 4:12 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > > The general principle is that R packages are only allowed to use what is > documented in the R help (? command) and in Writing R Extensions. The > former covers what is allowed from R code in extensions, the latter > mostly what is allowed from C code in extensions (with some references

Dear R devel, Apologies for these (most probably trivial) questions, doing my first attempt to call C from R (and actually learning C in the process). I need to pass a matrix to C, and after reading R-exts.pdf (many times), I was unable to find how to handle matrices at C-level... except for, what probably is the answer, that matrices are in fact vectors with dimensions. This is a sample code I

There is a bug in the command-line handling of 0.65.0 under Unix that may affect some users of R-inferior-mode under ESS, as that sets --no-readline as the first argument, and any arguments after that are ignored. The fix is simple: delete line 448 of src/unix/sys-common.c (`break;') and re-compile. The most used arguments are (I'm told) --vsize and --nsize. I find it more convenient to

Hi all, I am facing the necessity to parse R code from C-side. As a first approximation the goal would be a re-implementation of the R shell (not Rgui). I read the document at http://cran.r-project.org/doc/manuals/R-exts.html section 5.12, and the related source code example. I have some questions: 1. I need to declare the types and function signatures that I am going to use for this task

Hi folks, I apologise if this is in the documentation somewhere, but I can't seem to find it. I also did a search of CRAN without any success. I'm using R-1.8.1 (pre-compiled) on Windows 2000 with Rtools and mingw 2.0.0 (which includes gcc/g++ 3.2). I'm trying to link some C++ code from another application to R using the .Call interface and am experiencing some problems. I was

Because all drivers currently use gem objects for framebuffer planes, the virtual create_handle() is not required. This change adds a struct drm_gem_object *gems[4] field to drm_framebuffer and removes create_handle() function pointer from drm_framebuffer_funcs. The corresponding *_create_handle() function is removed from each driver. In many cases this change eliminates a struct *_framebuffer

Because all drivers currently use gem objects for framebuffer planes, the virtual create_handle() is not required. This change adds a struct drm_gem_object *gems[4] field to drm_framebuffer and removes create_handle() function pointer from drm_framebuffer_funcs. The corresponding *_create_handle() function is removed from each driver. In many cases this change eliminates a struct *_framebuffer

Because all drivers currently use gem objects for framebuffer planes, the virtual create_handle() is not required. This change adds a struct drm_gem_object *gems[4] field to drm_framebuffer and removes create_handle() function pointer from drm_framebuffer_funcs. The corresponding *_create_handle() function is removed from each driver. In many cases this change eliminates a struct *_framebuffer

Does anyone have an example of calling primitive or internal functions from C code that they would share with me? I am having trouble trying to figure out how to construct the proper arguments to pass to "do_subset_dflt" Here is the prototype: SEXP do_subset_dflt(SEXP call, SEXP op, SEXP args, SEXP rho); The R_FunTab from "names.c" gives some additional information on the

Does anyone have an example of calling primitive or internal functions from C code that they would share with me? I am having trouble trying to figure out how to construct the proper arguments to pass to "do_subset_dflt" Here is the prototype: SEXP do_subset_dflt(SEXP call, SEXP op, SEXP args, SEXP rho); The R_FunTab from "names.c" gives some additional information on the

Dear list: since it took me a little while to figure out how to make use of naresid, I thought that the below R code might be useful as an example on the help page. Regards, Markus # generate some data x1 <- runif(20) y <- 10 + 5*x1 + rnorm(20) summary(lm.0 <- lm(y ~ x1)) # append some NA's to y y <- c(y, rep(NA, 5)) # generate some further x1s x1 <- c(x1, runif(5)) #

Dear list: since it took me a little while to figure out how to make use of naresid, I thought that the below R code might be useful as an example on the help page. Regards, Markus # generate some data x1 <- runif(20) y <- 10 + 5*x1 + rnorm(20) summary(lm.0 <- lm(y ~ x1)) # append some NA's to y y <- c(y, rep(NA, 5)) # generate some further x1s x1 <- c(x1, runif(5)) #

Hi, As was discussed earlier in another thread and as documented in R-exts .Call() should not be interruptible by Ctrl-C. However the following code, which spends most of its time inside mkChar, turned out to be interruptible on RH-7.3 R-1.8.1 gcc-2.96: #include <Rinternals.h> #include <R.h> SEXP foo0(const SEXP nSexp) { int i, n; SEXP resSexp; if (!isInteger(nSexp))

Hi, Is there a way in which rsync's -z compression (zlib) utility can be benchmarked? I'm trying to compare the compression ratio between rsync and external compression tools like gzip and bzip2. Are there any advantages to using rsync's internal compression mechanism specified with the -z option compared to solely applying external compression i.e. bzip2 to the files and invoking

I'm not sure if this is the appropriate forum for questions regarding librsync, but couldn't find any others. I'm trying to get librsync working properly on Solaris 2.7 and 2.8 Sparc servers. The problem is that while librsync appears to compile cleanly, "make check" fails the sources.test. Does anyone have any insight as to why this might be? Might I need a specific

http://bugzilla.mindrot.org/show_bug.cgi?id=1242 Summary: GSSAPI Keyexchange support Product: Portable OpenSSH Version: 4.3p2 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Kerberos support AssignedTo: bitbucket at mindrot.org ReportedBy: simon at

This patch updates the files under popt/ to the latest vendor drop. The only change is the inclusion of a FreeBSD-specific patch to popt.c. This is needed in case somebody decides to build rsync on that platform without using the port. I'm not happy about the wording in popt/README.rsync so I may change it. The patch is available at http://www.catnook.com/rsync-popt-1.5.1.patch Comments