similar to: Invalidating inaccessible SEXP?

Displaying 20 results from an estimated 10000 matches similar to: "Invalidating inaccessible SEXP?"

2010 Nov 15
1
SEXP and slots
Hello, Since people have whisperred about Rcpp, I'd like to play too. > On 11/15/2010 07:45 AM, Patrick Leyshock wrote: >> Very helpful, thank you. >> >> A couple other questions, please: >> >> 1. I've got a function written in C, named "my_c_function". In my R >> code I call this function, passing to it an INTSXP and a STRSXP, >>
2020 Sep 06
8
some questions about R internal SEXP types
Hello, I am writing an R/Go interoperability tool[1] that work similarly to Rcpp; the tool takes packages written in Go and performs the necessary Go type analysis to wrap the Go code with C and R shims that allow the Go code to then be called from R. The system is largely complete (with the exception of having a clean approach to handling generalised attributes in the easy case[2] - the less
2018 Dec 13
2
Documentation examples for lm and glm
Hello, something that has been on my mind for a decade or two has been the examples for lm() and glm(). They encourage poor style because of mismanagement of data frames. Also, having the variables in a data frame means that predict() is more likely to work properly. For lm(), the variables should be put into a data frame. As 2 vectors are assigned first in the general workspace they should be
2020 Sep 08
2
some questions about R internal SEXP types
On Tue, 2020-09-08 at 12:08 +0200, Tomas Kalibera wrote: > I am not sure if I understand correctly, but if you were accessing > directly the memory of SEXPs from Go implementation instead of > calling > through exported access functions documented in WRE, that would be a > really bad idea. Of course fine for research and experimentation, but > the internal structure can and does
2018 Aug 09
2
SIGSEGV in R_RunWeakRefFinalizer, object allocated with Rcpp
Thanks, Tomas, Luke, for the clarifications. Then, I have another question. But first, let me introduce how I ended up here, because obviously I just don't go around dyn.unloading things that I've just compiled. I was testing a package with valgrind. Everything ok, no leaks. Great. But I'm always suspicious (probably unjustifiably) of all the memory that is reported as "still
2017 Feb 14
2
Mailbox suddenly inaccessible
Hi, out of the sudden I've an inaccessible folder with Dovecot 2.2.27 (c0f36b0) from Debian Jessy backports. $ doveadm mailbox list -u mail at example.com INBOX/Erledigt INBOX/Erledigt/Erledigt INBOX/Versicherung gesendet Sent INBOX However, it is not accessible any more, my IMAP client tells me: "STATUS: Mailbox doesn't exist: INBOX/Erledigt" Also: $ doveadm search -u mail
2014 Nov 25
2
[PATCH] check-gnu-efi.sh: print the output of build-gnu-efi.sh
> _ The gnu-efi git repository is currently partially unavailable. Trying > to retrieve older commits (as the one used in the official release of > Syslinux 6.03 stable) might succeed, but, at this moment, trying to > retrieve the official gnu-efi master head will fail. Update: after several days, the gnu-efi master head is now available again. I do not discard the possibility
2002 May 28
2
MYGROUP inaccessible
High gurus, Je souhaite mettre en place un serveur samba lorsque je vais dans le voisinnage r?seau je vois bien le partage MYGROUP cependantlorsque je veux y acc?der j'ai une erreur du type : MYGROUP est inaccessible. l'ordinateur ou le nom de partage n'a pas ?t? trouv? !! controler votre entr? et r??ssayez !! Une id?e ? # Samba config file created using SWAT # from 130.0.10.3
2014 Oct 17
1
Holding a large number of SEXPs in C++
Background: I have an algorithm which produces a large number of small polygons (of the spatial kind) which I would like to use within R using objects from sp. I can't predict the exact number of polygons a-priori, the polygons will be grouped into regions, and each region will be filled sequentially, so an appropriate C++ 'framework' (for the point of illustration) might be: typedef
2008 Mar 05
1
SEXP size management.
Hi, Trying to decrease the size of a SEXP variable without reassigning values individually in a loop. So far, I've tried using Realloc, as the follow source demonstrates: SEXP dothis() { SEXP Rblah; PROTECT(Rblah = NEW_INTEGER(6)); int* blah = INTEGER(Rblah); blah[0] = 1; blah[1] = 2; blah[2] = 3; Realloc(Rblah, 3, INTEGER); UNPROTECT(1); return(Rblah); } According to the
2006 Sep 28
1
eval(SEXP fn,SEXP rho) in C++ code
Hi r-devel, I am working on a R extension. I am writing the function in C++, and in my function it is required a R function object from the user. This R function object will be evaluated thousand of times in my C++ code. I generated the shared library and I loaded it on R. I did several experiments in order to compare the speed of my compiled code vs the speed of the equivalent interpreted code.
2007 Nov 15
1
Nested SEXP functions
Hey All, I was wondering if I could solicit a little advice. I have been experiencing some quirkiness in my C code through .Call. Unfortunately, my program is rather large, so I'm trying to create a brief example. Yet before I do, I thought maybe a conceptual question would be sufficient. Basically, I'm writing up a multidimensional Gaussian likelihood (with spatial covariances and
2008 Feb 19
1
level of mutability for the type of a SEXP
Dear list, I am writing C code to interface with R, and I would like to know the level of mutability for the type of a SEXP. I see that there is a macro/function TYPEOF(), and that it can be used as an l-value, as well as a macro/function SET_TYPEOF(). My question is "should the type be considered immutable, or it can it change after the SEXP has been created and used for a while ?".
2010 Sep 28
1
How to convert SEXP to double
Hello All, A simple question. I get some return from the R in my C++ program (via Rcpp package). The result come, as SEXP and it should be a simple numeric variable. How to convert it to double? The code, what i use: stringstream ss; ss << "p <- predict(fit_ar11, n.ahead = 2, doplot=FALSE);" << "p$pred[1]"; SEXP ans; int iRet =
2010 Feb 20
1
how to create a SEXP which could be accessed in embedded R
Hi all, I am not familiar with writing R extensions. In a C program, I want to create a SEXP and access it in embedded R. How to let the embedded engine know there's a new vector? For example, after creating a SEXP, parsing 'ls()' in embedded R and then evaluating, STRSXP returned will contain the name of the SEXP. Any help would be appreciated. Regards, Spiral [[alternative HTML
2014 Jun 26
1
using 2D array of SEXP for creating dataframe
Hi , For our production package i need to create a dataframein C . So I wrote the following code SEXP dfm ,head,df , dfint , dfStr,lsnm; *SEXP valueVector[2];* char *ab[3] = {"aa","vv","gy"}; int sn[3] ={99,89,12}; char *listnames[2] = {"int","string"}; int i,j; //============================= PROTECT(df = allocVector(VECSXP,2));
2011 Sep 13
1
Getting Rcpp SEXP data in C++
Friends I am looking at Rcpp and I am a bit stuck on a simple matter. (I am calling R from c++, if there is a better way...) Given this simple example using the TTR package and the SMA function which returns a simple moving average.... Rcpp::NumericVector rv; for(int i = 0; i < 100; i++){ rv.push_back(rand()); } Rcpp::Environment TTR("package:TTR");
2003 Dec 17
1
Accessing row and col names of SEXP objects
Can someone lend me a hand with extracting the dimnames from a SEXP? I've looked through R-exts, but I couldn't find an example. Here is the code I'm using to grab the jth column name and print it, but the colnames I'm getting are garbage. None of the following are working. void printInfo(SEXP ts) { int j; for (j=0; j<col; j++) {
2010 Oct 27
2
must .Call C functions return SEXP?
For using R's .Call interface to C functions, all the examples I've seen have the C function return type SEXP. Why? What does R actually do with this return type? What happens if I *don't* return a SEXP? Reason I ask, is I've written some R code which allocates two long lists, and then calls a C function with .Call. My C code writes to those two pre-allocated lists, thus, I
2020 Sep 08
0
some questions about R internal SEXP types
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 to Fortran). If you are implementing a Go interface for writing R packages, such Go interface should thus only