検索
- BugTrack-Ｒ備忘録/28 - SEXP test05(SEXP Rn, SEXP Ra, SEXP Rw, SEXP Rinfo){
- BugTrack-Ｒ備忘録/29 - SEXP levenshtein_0(SEXP l1, SEXP l2, SEXP s1, SEXP s2, SEXP d)
- BugTrack-Ｒ備忘録/30 - SEXP strSplit(SEXP str)
- BugTrack-Ｒ備忘録/31 - *allocVector(SEXPTYPE type, R_len_t length)
- BugTrack-Ｒ備忘録/32 - SEXP parseString(char *s, int *parts, ParseStatus *status) {
- BugTrack-Ｒ備忘録/34 - SEXP eval_fun02(SEXP a, SEXP rho)
- BugTrack-Ｒ備忘録/53 - *C type Rcomplex is a structure with double members r and i defined in the header file ‘R_ext/Complex.h’ included by ‘R.h’. (On most platforms which have it, this is compatible withe C99 double complex type.) Only a single character string can be passed to or from FORTRAN, and the success of this is compiler-dependent. Other R objects can be passed to .C, but it is better to use one of the other interfaces. An exception is passing an R function for use with call_R, when the object can be handled as void * en route to call_R, but even there .Call is to be preferred. Similarly, passing an R list as an argument to a C routine should be done using the .Call interface. If one does use the .C function to pass a list as an argument, it is visible to the routine as an array in C of SEXP types (i.e., SEXP *). The elements of the array correspond directly to the elements of the R list. However, this array must be treated as read-only and one must not assign values to its elements within the C routine ― doing so bypasses R’s memory management facilities and will corrupt the object and the R session.
- BugTrack-Ｒ備忘録/56 - SEXP convolve2(SEXP a, SEXP b)
- BugTrack-Ｒ備忘録/57 - SEXP test001(SEXP a){
- BugTrack-Ｒ備忘録/58 - SEXP Rdgemv01(SEXP ex_A, SEXP ex_x, SEXP ex_y)
- Menu - *[sexp|http://phoenixx.sakura.ne.jp/R/wiki.cgi?word=sexp&t=and&action=SEARCH]