Hi Cesar, it works both ways, and there is an old R C API and more modern C++ implementations (with C headers too) for the use case here: - call R from C(++). or better: - call R from PicoLisp via (native) C (calls) See my last answer to Alex to see that the call to R actually works. Cheers Thorsten.
Am Di., 6. Apr. 2021 um 22:20 Uhr schrieb Cesar Rabak <cesar.ra...@gmail.com >: > Hi Thorsten, > > The quote you copied here (coming from the ref. of yours R's C Interface), > describes IIUC a structure, more accurately the model of, for calling > "foreing" C functions in R and not the converse. > > The way to call R functions in picolisp would be to call the functions > made available through the API, in case of R a process similar to FFI using > as reference the include files, wouldn't? > > HTH > -- > Cesar Rabak > > > On Mon, Apr 5, 2021 at 4:30 PM Thorsten Jolitz <tjol...@gmail.com> wrote: > >> Hello List, >> I wonder how to deal with the R SEXP Data structure in native calls. >> >> *"Technically, [a SEXP] is a pointer to a structure with typedef SEXPREC
