search for: wre

...ments without breaking client code that has come to depend on these details. The API of C entry points that can be used in R extensions, both for packages and embedding, has evolved organically over many years. The definition for the current release expressed in the Writing R Extensions manual (WRE) is roughly: An entry point can be used if (1) it is declared in a header file in R.home("include"), and (2) if it is documented for use in WRE. Ideally, (1) would be necessary and sufficient, but for a variety of reasons that isn't achievable, at least not in the near ter...

...client code that has come to depend on these details. > > The API of C entry points that can be used in R extensions, both for > packages and embedding, has evolved organically over many years. The > definition for the current release expressed in the Writing R > Extensions manual (WRE) is roughly: > > An entry point can be used if (1) it is declared in a header file > in R.home("include"), and (2) if it is documented for use in WRE. > > Ideally, (1) would be necessary and sufficient, but for a variety of > reasons that isn't achievable,...

...client code that has come to depend on these details. > > The API of C entry points that can be used in R extensions, both for > packages and embedding, has evolved organically over many years. The > definition for the current release expressed in the Writing R > Extensions manual (WRE) is roughly: > > An entry point can be used if (1) it is declared in a header file > in R.home("include"), and (2) if it is documented for use in WRE. > > Ideally, (1) would be necessary and sufficient, but for a variety of > reasons that isn't achievable,...

...client code that has come to depend on these details. > > The API of C entry points that can be used in R extensions, both for > packages and embedding, has evolved organically over many years. The > definition for the current release expressed in the Writing R > Extensions manual (WRE) is roughly: > > An entry point can be used if (1) it is declared in a header file > in R.home("include"), and (2) if it is documented for use in WRE. > > Ideally, (1) would be necessary and sufficient, but for a variety of > reasons that isn't achievable,...

...details. > > The API of C entry points that can be used in R extensions, both > for > packages and embedding, has evolved organically over many years. > The > definition for the current release expressed in the Writing R > Extensions manual (WRE) is roughly: > > ? ? ?An entry point can be used if (1) it is declared in a > header file > ? ? ?in R.home("include"), and (2) if it is documented for use > in WRE. > > Ideally, (1) would be necessary and sufficient, but for a >...

...The API of C entry points that can be used in R extensions, both > > for > > packages and embedding, has evolved organically over many years. > > The > > definition for the current release expressed in the Writing R > > Extensions manual (WRE) is roughly: > > > > An entry point can be used if (1) it is declared in a > > header file > > in R.home("include"), and (2) if it is documented for use > > in WRE. > > > > Ideally, (1) would be necessary an...

...g 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 current description it seems restricted to 2 or 3 letter ISO-639 codes such as "en" or "eng". WRE also mentions rfc-5646, which refers to ISO 3166-1 for region/country subtags but it is unclear if th...

If a package has importClassesFrom(P, C) in its NAMESPACE, then should it _also_ have importClassesFrom(P, <superclasses of C exported from P>) importClassesFrom(Q, <superclasses of C exported from Q>) ## and so on ... ? I think that WRE could be more clear on this point, and in any case I _think_ that the answer is yes. Notably, I think that this rule would resolve some of the problems with stale caches that I described in this thread from September: https://stat.ethz.ch/pipermail/r-devel/2022-September/081971.html I'v...

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 change at any time, otherwise we > would not be able to develop nor maintain R. Such direct access > bypassing WRE would likely be a clear case for rejection in...

...d 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 experience lend a helping hand please? A reference (so I can continue learning) would also be appreciated. Thanks... -=d David Thompson, Ph.D., P.E., D.WRE, CFM Civil Engineer/Hydrologist

Hello, This is what "Writing R extensions" currently says about R_atof and R_strtod: >> Function: void R_atof (const char* str) >> Function: void R_strtod (const char* str, char ** end) >> >> Implementations of the C99/POSIX functions atof and strtod which >> guarantee platform-dependent behaviour, including always using the >> period as the decimal

...ortschak wrote: > 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 change at any time, otherwise we >> would not be able to develop nor maintain R. Such direct access >> bypassing WRE would likely be a clear case...

...se to write R extensions has evolved organically over many years. The current state is certainly not ideal: There are entry points in installed headers that might be available; but to find out if they are in fact available requires reading prose text in the header files and in WRE. Trying to fine-tune wording in WRE, or add a lot of additional entries is not really a good or realistic way forward: WRE is both documentation and tutorial and more legalistic language/more complete coverage would make it less readable and still not guarantee completeness or clarity. We would b...

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

...c and result in an R > error. The necessary interface to R for allocations is only eight > functions[1]. 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 change at any time, otherwise we would not be able to develop nor maintain R. Such direct access bypassing WRE would likely be a clear case for rejection in CRAN for this...

> 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 words enclosed in single quotes: names of packages and libraries should be quoted in titles. ..and it is the "single word" bit that gets you. AFAICT, the iss...

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: >...

...nderscore is allowed. >> >> Given that I've obeyed the RTFM rule, I'm wondering what to do now. > > Presumably you should ask the CRAN maintainers? That seems to > be the only possible answer -- I don't think anyone else can guess > very accurately ... From WRE: "Refer to other packages and external software in single quotes, and to book titles (and similar) in double quotes." Other non-English usage (as documented for the Description field; this inlcudes function names) can also be used in single quotes. Best, Uwe Ligges > > Ben...

...ges (e.g. applications embedding R), are different sets. But I suspect this discussion is most relevant to R package authors who wish to submit their packages to CRAN. > > There are some 500 entry points in the R shared library that are in > > the installed headers but not mentioned in WRE. These would need to > > be reviewed and adjusted. > > Is there a way for outsiders to help? For example, would it help to > produce the linking graph (package P links to entry points X, Y)? I > understand that an entry point being unpopular doesn't mean it > shouldn't...

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:...