I believe you've got _some_ time. As of the changes in 3.4.0 the verbiage is:
R CMD check --as-cran now NOTEs if the package does not register
its native routines or does not declare its intentions on (native)
symbol search. (This will become a WARNING in due course.)
And I think it's
Dear Duncan,
Thank you very much for your email. That worked fine!
-Tolis.
On Mon, 18 Feb 2019 at 15:41, Duncan Murdoch
wrote:
> On 18/02/2019 6:08 a.m., Τόλης Χαλκής wrote:
> > I am developing a Rcpp package in order to make a submission to CRAN. I
> use
> > modules for 4 C++ classes. I have
On 18/02/2019 6:08 a.m., Τόλης Χαλκής wrote:
I am developing a Rcpp package in order to make a submission to CRAN. I use
modules for 4 C++ classes. I have used the prompt function (`prompt(yada,
"yada-module.Rd")`) using the names of my modules, in order to document the
exposed classes. But I sti
I am developing a Rcpp package in order to make a submission to CRAN. I use
modules for 4 C++ classes. I have used the prompt function (`prompt(yada,
"yada-module.Rd")`) using the names of my modules, in order to document the
exposed classes. But I still get a warning when I perform the check using
On 18 Feb 2019, at 8:13, Stefan McKinnon Høj-Edwards wrote:
* is it possible to import a set of *.Rd man documentation files into
my
R session?
This may be what you want:
https://cran.r-project.org/web/packages/Rd2roxygen/index.html
Although my experience a while back was that some manual
Hi Iaw,
Hadley's book is generally a good starting point. For an overview of the
roxygen2, I have a summary on http://www.iysik.com/r/roxygen2, which is but
a small addition to the current sphere of knowledge.
Re. your questions:
> * is it possible to import a set of *.Rd man documentation files
