search for: funapi

Hi all, I've noticed some peculiarities in the tools:::funAPI output that complicate its programmatic use a bit. - Is it for remapped symbol names (with Rf_ or the Fortran underscore), or for unmapped names (without Rf_ or the underscore)? I see that the functions marked in WRE are almost all (except Rf_installChar and Rf_installTrChar) unmapped. This m...

...defines.h") Error in regmatches(lines, gregexec(rx, lines, perl = TRUE))[[1]][3, ] : incorrect number of dimensions On Mon, Jul 15, 2024 at 10:32?AM Ivan Krylov via R-devel <r-devel at r-project.org> wrote: > > Hi all, > > I've noticed some peculiarities in the tools:::funAPI output that > complicate its programmatic use a bit. > > - Is it for remapped symbol names (with Rf_ or the Fortran > underscore), or for unmapped names (without Rf_ or the underscore)? > > I see that the functions marked in WRE are almost all (except > Rf_installChar and R...

...nswered unambiguously. The annotations so far mostly reflect my reading or WRE and may be revised as they are reviewed by others. The annotated document can be used for programmatically identifying what is currently considered part of the C API. The result so far is an experimental function tools:::funAPI(): > head(tools:::funAPI()) name loc apitype 1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h eapi 2 alloc3DArray WRE api 3 allocArray WRE api 4 allocLang...

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 to install R-devel to check. Best, Yutani 2024?6?6?(?) 23:47 luke-tierney--- via R-devel <r-devel at r-project.org>: > This is an update on some current work on the C API for use in R > extension...

...y. The > annotations so far mostly reflect my reading or WRE and may be revised > as they are reviewed by others. The annotated document can be used for > programmatically identifying what is currently considered part of the C > API. The result so far is an experimental function tools:::funAPI(): > > > head(tools:::funAPI()) > name loc apitype > 1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h eapi > 2 alloc3DArray WRE api > 3 allocArray WRE api &g...

...y. The > annotations so far mostly reflect my reading or WRE and may be revised > as they are reviewed by others. The annotated document can be used for > programmatically identifying what is currently considered part of the C > API. The result so far is an experimental function tools:::funAPI(): > > > head(tools:::funAPI()) > name loc apitype > 1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h eapi > 2 alloc3DArray WRE api > 3 allocArray WRE api &g...

...E and may be > revised > as they are reviewed by others. The annotated document can be > used for > programmatically identifying what is currently considered part > of the C > API. The result so far is an experimental function > tools:::funAPI(): > > ? ? ?> head(tools:::funAPI()) > ? ? ? ? ? ? ? ? ? ? ?name? ? ? ? ? ? ? ? ? ? loc apitype > ? ? ?1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h? ? eapi > ? ? ?2? ? ? ? alloc3DArray? ? ? ? ? ? ? ? ? ? WRE? ? ?api > ? ? ?3? ? ? ? ? allocArray? ?...

...d > > as they are reviewed by others. The annotated document can be > > used for > > programmatically identifying what is currently considered part > > of the C > > API. The result so far is an experimental function > > tools:::funAPI(): > > > > > head(tools:::funAPI()) > > name loc apitype > > 1 Rf_AdobeSymbol2utf8 R_ext/GraphicsDevice.h eapi > > 2 alloc3DArray WRE api > >...