search for: calldef

...2074: xx <- .Call(splitString, x, ' -/"()\n') R-3-4-trunk/src/library/tools/src/text.c:264:SEXP splitString(SEXP string, SEXP delims) R-3-4-trunk/src/library/tools/src/tools.h:45:SEXP splitString(SEXP string, SEXP delims); R-3-4-trunk/src/library/tools/src/init.c:53: CALLDEF(splitString, 2), Doing that is perfectly legal according to help(".Call"), and interestingly, it apparently does NOT matter whether that code puts quotes around the splitString or not - I tried it, and it made no difference. Is it generally the case the users MUST NOT define R functions...

...); R_RunExitFinalizers(); R_gc(); does not help either... However I can trigger the problem on the R cmdline when I do: .Call("R_isMethodsDispatchOn", 1,2, PACKAGE = "base") : also looking at src/main/registration.c I don't see a reason why it should be wrong: CALLDEF(R_isMethodsDispatchOn, 1)... Any ideas? Soeren

Hi, I have followed the recommended steps for creating a package (rctest). As of now, my goal is simply to understand how various pieces fit together. The package includes: (1) C code with source in sub-directories, compiled to create a static library. (a) There is a single C-struct (dns) a simple 'matrix': {int m; int n; double *d;} (b) C code to create random matrix of a certain size.

Dear all, I’m not sure if it is O.K. to ask this question here. But where can I find the code for the function ‘C_Cdqrls’ which is called by the R function ‘lsfit‘. Thank you all. Sorry for being naïve if so. -------------------- Ziqiang Zhao 2013-04-23 [[alternative HTML version deleted]]