Re: [R-pkg-devel] Rcpp with clang++ -stdlib=libc++ ?

2020-09-13 Thread Dr . Jens Oehlschlägel
Thank you Dirk and Kevin, that was very helpful and > sudo apt install libc++-dev libc++abi-dev did the job! Great, this was very important to me. Thanks again Jens On 13.09.20 02:55, Kevin Ushey wrote: > My understanding is that many Linux OSes package the clang compiler, the >

Re: [R-pkg-devel] Use of `:::` in a package for code run in a parallel cluster

2020-09-13 Thread Martin Morgan
At least in the 'parallel' package library(parallel) cl = makePSOCKcluster(2) and because of the nature of the R language, the entire namespace is exported, analogous to baz <- local({ foo <- function() 2 function(...) foo() }) so making a package function baz available makes all

Re: [R-pkg-devel] CRAN incoming checks email

2020-09-13 Thread Uwe Ligges
On 13.09.2020 21:22, David Kepplinger wrote: Dear List-Members: The email from the automatic incoming checks says to "reply-all" in case one suspects a false-positive, yet the reply-to header is set only to " cran-submissi...@r-project.org". My email program (just as myself) interprets this

Re: [R-pkg-devel] Use of `:::` in a package for code run in a parallel cluster

2020-09-13 Thread David Kepplinger
Thank you all for the discussion and suggestions. so making a package function baz available makes all functions in the > package available -- a function in the package already has access to other > functions in the namespace, whether those functions are exported or not, so > there is no need to

Re: [R-pkg-devel] Use of `:::` in a package for code run in a parallel cluster

2020-09-13 Thread Joshua Ulrich
On Sun, Sep 13, 2020 at 3:19 PM Duncan Murdoch wrote: > > On 13/09/2020 3:51 p.m., David Kepplinger wrote: > > Dear list members, > > > > I submitted an update for my package and got automatically rejected by the > > incoming checks (as expected from my own checks) for using `:::` calls to > >

[R-pkg-devel] Use of `:::` in a package for code run in a parallel cluster

2020-09-13 Thread David Kepplinger
Dear list members, I submitted an update for my package and got automatically rejected by the incoming checks (as expected from my own checks) for using `:::` calls to access the package's namespace. "There are ::: calls to the package's namespace in its code. A package *almost* never needs to

Re: [R-pkg-devel] Use of `:::` in a package for code run in a parallel cluster

2020-09-13 Thread Duncan Murdoch
On 13/09/2020 3:51 p.m., David Kepplinger wrote: Dear list members, I submitted an update for my package and got automatically rejected by the incoming checks (as expected from my own checks) for using `:::` calls to access the package's namespace. "There are ::: calls to the package's

[R-pkg-devel] CRAN incoming checks email

2020-09-13 Thread David Kepplinger
Dear List-Members: The email from the automatic incoming checks says to "reply-all" in case one suspects a false-positive, yet the reply-to header is set only to " cran-submissi...@r-project.org". My email program (just as myself) interprets this as "reply-all means replying only to

Re: [R-pkg-devel] Use of `:::` in a package for code run in a parallel cluster

2020-09-13 Thread Wang, Zhu
Apologize if I hijack this thread, but the use of ::: is something I was puzzled. I tried Duncan's solution in my R package mypkg, something like: pkg::callInternal("foo", args) R CMD check mypkg * checking dependencies in R code ... WARNING '::' or ':::' import not declared from: ‘pkg' I