Re: [Rd] clarifying and adjusting the C API for R

2024-06-18 Thread luke-tierney--- via R-devel
Another quick update: Over 100 entry points used in packages for which it was safe to do so have now been marked as part of an API (in some cases after adding error checking of arguments). These can be used in package C code, with caveats for ones considered experimental or intended for embedded

Re: [Rd] clarifying and adjusting the C API for R

2024-06-09 Thread Travers Ching
Hi Luke, thanks for all your work on R! I'd like to ask specifically about R_serialize / R_unserialize (and associated helper functions). These are used by at least a handful of packages and I don't see them in the list from Yutani. Are these API functions considered "stable"? Best, Travers On

Re: [Rd] clarifying and adjusting the C API for R

2024-06-08 Thread Hiroaki Yutani
Thanks so much for your wonderful work, Luke! I didn't expect such a clarification to happen this soon. This is really great. For convenience, I created a quick web page to search the result of tools:::funAPI(). https://yutannihilation.github.io/R-fun-API/ Hope this helps those who are too lazy

Re: [Rd] clarifying and adjusting the C API for R

2024-06-07 Thread Steven Dirkse
Thanks for sharing this overview of an interesting and much-needed project. You mention that R exports about 1500 symbols (on platforms supporting visibility) but this subject isn't mentioned explicitly again in your note, so I'm wondering how things tie together. Un-exported symbols cannot be pa

Re: [Rd] clarifying and adjusting the C API for R

2024-06-07 Thread Hadley Wickham
Thanks for working on this Luke! We appreciate your efforts to make it easier to tell what's in the exported API and we're very happy to work with you on any changes needed to tidyverse/r-lib packages. Hadley On Thu, Jun 6, 2024 at 9:47 AM luke-tierney--- via R-devel < r-devel@r-project.org> wrot