Hi,
I tried to understand how to check memory access of an R package with
C code; see
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Checking-memory-access
I'm about 90% sure I understood WRE Section 4.3.2 about valgrind. In essence:
1) When configuring R before make, use the confi
On Sun, Jun 17, 2018 at 2:13 AM Uwe Ligges
wrote:
>
>
>
> On 16.06.2018 21:46, Marius Hofert wrote:
> > Dear DevelopeRs,
> >
> > Is there a recommended procedure for addressing "Additional issues" if
> > they appear on CRAN checks?
> >
> &g
Dear DevelopeRs,
Is there a recommended procedure for addressing "Additional issues" if
they appear on CRAN checks?
Say you have some C code in a package which checks fine (Status OK for
all flavors) but shows "Additional issues" due to a potential memory
problems. One can compile an R version co
Hi,
... as promised, here is essentially what Uwe mentioned: Under my
setup, it is acceptable that 'loon' (package 'bar') appears in
Suggests and that the DESCRIPTION text mentions how to install 'loon'
(from github; provide a link in the text with '<>') if the user wants
to do the plotting with '
> As already suggested:
> - create a drat repository,
> - place a copy of loon (from its repo source or the Archive section) in it
> - add the repo to Additional_repositories
> - using Suggests: is now permissible as the package is now useable
> - the ':::' not declared warning should now go a
On Sun, Feb 25, 2018 at 11:16 AM, Rolf Turner wrote:
>
> Marius:
>
> Can you not, instead of
>
>> if(pkg == "loon" && !requireNamespace("loon", quietly = TRUE))
>> stop("Package 'loon' is not available.")
>
> do something like:
>
> if(pkg == "loon" && !requireNamespace("loon", quietly = TR
>> It does -- except for the 'warning':
>>
>> '::' or ':::' import not declared from: ‘bar’
>> 'loadNamespace' or 'requireNamespace' call not declared from: ‘bar’
>
> That's because 'bar' is not in Suggests.
Thinking a bit about it, the reference to
https://cran.r-project.org/doc/manuals/r-release
On Sun, Feb 25, 2018 at 1:41 AM, Duncan Murdoch
wrote:
> On 24/02/2018 7:26 PM, Marius Hofert wrote:
>> On Sun, Feb 25, 2018 at 1:09 AM, Dirk Eddelbuettel wrote:
>>>
>>> On 25 February 2018 at 00:45, Marius Hofert wrote:
>>> | A package 'foo' use
On Sun, Feb 25, 2018 at 1:09 AM, Dirk Eddelbuettel wrote:
>
> On 25 February 2018 at 00:45, Marius Hofert wrote:
> | A package 'foo' uses a package 'bar' (in Imports). 'bar' has been
> | archived and the maintainer of 'foo' was asked to fix
>
> if (requireNamespace("bar", quietly = TRUE)) {
># do the good stuff
> } else {
># do some less good substitute
> }
>
> without generating an error anywhere.
Hi Duncan,
thanks for helping.
I use the above
>
>
>>
>> '::' or ':::' import not declared from: ‘bar’
>> 'loadNamespace' or '
Hi,
A package 'foo' uses a package 'bar' (in Imports). 'bar' has been
archived and the maintainer of 'foo' was asked to fix the dependency
on 'bar' according to WRE 1.1.3.1.
Working with 'bar::' everywhere (and requireNamespace("bar", quietly =
TRUE)), as well as moving 'bar' from Imports to Sugg
Hi,
I have a function A which calls a function B. B accepts an argument
'FUN' (a function). Depending on the choice of package, A constructs
FUN and passes it on to B:
A <- function(x, pkg = c("pkg1", "pkg2", "pkg3"), ...) {
pkg <- match.arg(pkg)
FUN <- switch(pkg,
"pkg1" = {
On Sat, May 21, 2016 at 7:45 PM, Henrik Bengtsson
wrote:
> On Sat, May 21, 2016 at 8:22 AM, Marius Hofert
> wrote:
>> Hi,
>>
>> I have (co-)developed two packages: 'qrmtools' and 'qrmdata'. The
>> latter contains data sets and is currently only
Hi,
I have (co-)developed two packages: 'qrmtools' and 'qrmdata'. The
latter contains data sets and is currently only available on R-Forge
(as it is larger than 5MB and thus not accepted for CRAN [although
there are much larger packages, but that's a different story...]).
'qrmtools' contains mainl
14 matches
Mail list logo
