similar to: safe shutdown/startup problems

This is an update on some current work on the C API for use in R extensions. The internal R implementation makes use of tens of thousands of C entry points. On Linux and Windows, which support visibility restrictions, most of these are visible only within the R executble or shared library. About 1500 are not hidden and are visible to dynamically loaded shared libraries, such as ones in packages,

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 at r-project.org> wrote: > This is an update on some current work on the C API for use in R >

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

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 part of the API - how would people use them in this case? In a perfect world the set of

On Fri, 7 Jun 2024, Steven Dirkse wrote: > You don't often get email from sdirkse at gams.com. Learn why this is important > 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

Would it be reasonable to move the non-API stuff that cannot be hidden into header files inside a "details" directory (or some other specific naming scheme)? That's what I use when I need to separate a public API from an internal API. On Fri, Jun 7, 2024 at 7:30?AM luke-tierney--- via R-devel <r-devel at r-project.org> wrote: > > On Fri, 7 Jun 2024, Steven Dirkse

I am looking for the appropriate field to let package authors to declare the pkg documentation language for spell checkers. The most important case is to specify a preference between "en-US" or "en-GB" which can be used by the hunspell or spelling pkg to select the appropriate dictionary. WRE defines the "Language" field for documentation language, but from the

On Tue, 2020-09-08 at 12:08 +0200, Tomas Kalibera wrote: > I am not sure if I understand correctly, but if you were accessing > directly the memory of SEXPs from Go implementation instead of > calling > through exported access functions documented in WRE, that would be a > really bad idea. Of course fine for research and experimentation, but > the internal structure can and does

OK, this should be trivial but I'm not finding it. I want to compress the test, if (i==7 | i==10 | i==30 | i==50) {} into something like if (i in c(7,10,30,50)) {} so I can build a "excludes" vector excludes <- c(7,10,30,50) and test if (i in excludes) {} However, I'm not finding a clue on how to accomplish this, if it can be done. Would someone with more R

Hello, I am writing an R/Go interoperability tool[1] that work similarly to Rcpp; the tool takes packages written in Go and performs the necessary Go type analysis to wrap the Go code with C and R shims that allow the Go code to then be called from R. The system is largely complete (with the exception of having a clean approach to handling generalised attributes in the easy case[2] - the less

> On 25 Apr 2015, at 13:11 , Prof J C Nash (U30A) <nashjc at uottawa.ca> wrote: > > Hendrik pointed out it was the parentheses that gave the complaint. > Single quotes and no parentheses seem to satisfy R CMD check. Perhaps > that needs to be in the WRE. Well, it is in ?toTitleCase: ...However, unknown technical terms will be capitalized unless they are single

On 24.04.2015 22:44, Ben Bolker wrote: > Prof J C Nash (U30A <nashjc <at> uottawa.ca> writes: > >> >> I was preparing a fix for a minor glitch in my optimx package and R CMD >> check gave an error that the title was not in title case. > > [snip] to make Gmane happy ... > >> I have found >> >> A Replacement and Extension of the

On Wed, 24 Apr 2024, Hadley Wickham wrote: >> >> >> >>>>> That is not true at all - the presence of header does not constitute >>>> declaration of something as the R API. There are cases where internal >>>> functions are in the headers for historical or other reasons since the >>>> headers are used both for the internal

I take Duncan's point but would second the motion to have WRE clarify how static vignettes are supposed to work; it's a topic I am repeatedly confused about despite being an experienced package maintainer. If knowledgeable outsiders compiled a documentation patch would it be likely to be considered ...?? On 11/1/20 2:29 PM, Duncan Murdoch wrote: > On 01/11/2020 1:02 p.m., Alexandre

On Thu, Apr 25, 2024 at 4:24?AM Ivan Krylov via R-devel <r-devel at r-project.org> wrote: > > On Wed, 24 Apr 2024 15:31:39 -0500 (CDT) > luke-tierney--- via R-devel <r-devel at r-project.org> wrote: > > > We would be better off (in my view, not necessarily shared by others > > in R-core) if we could get to a point where: > > > > all entry points

On 05/08/2010 8:46 PM, David B. Thompson, Ph.D., P.E., D.WRE, CFM wrote: > On Aug 5, 2010, at 5:20 PM, Duncan Murdoch wrote: > >> On 05/08/2010 7:18 PM, David B. Thompson, Ph.D., P.E., D.WRE, CFM wrote: >>> I'm running R 2.11.1 (MacBook Pro and OS X 10.6.4) and am trying to set a line type in the contour() function. What I did was: >>> >>>> >

Dear List, I'm having considerable trouble setting up my environment (Linux, Fedora 16, Bash) to build and check packages under R Under Development (r61660). I'm doing this to better get a handle on difference in the output from running checks on examples in one of my packages. Note I compiled R Under Development myself The problem I am now having is whenever I try to build my analogue

Noted Duncan and TRUE... I cannot do more immediately unfortunately, that is always the issue of asking a last minute panic attack question before teaching a course involving the package... I do have /doc in my .Rbuildignore for reasons I can no longer remember... I will dig and create a MRE/reprex. The students will download heavy packages, but they probably won't notice. *Apologies* In the

useR's, Does any one know if there is a size limitation on the data frames that can be included in R packages. I have a data set in a text file that I would like to include in a package I am building and it is 8.5 MB in size. Will this be problematic? Is the process for including data sets in packages documented in WRE? Thanks, dxc -- View this message in context:

Hi Ivan Can you please clarify what input files should be used with your proposed function? I tried a few files in r-svn/src/include and one of them gave me an error. > getdecl("~/R/r-svn/src/include/R.h") [1] "R_FlushConsole" "R_ProcessEvents" "R_WaitEvent" > getdecl("~/R/r-svn/src/include/Rdefines.h") Error in regmatches(lines,