On Tue, Sep 24, 2019 at 11:13 AM Gábor Csárdi wrote:
>
> I believe that this is because if it is outside of a function, then it
> runs at INSTALL time, and codetools checks the installed code, i.e.
> the function objects typically, and the checks never see the
> globalVariables() call.
That
Hi All:
A few days ago I had to resubmit because an external URL I was using in my
vignette changed and the nightly builds were issuing warnings. This morning a
user reported a bug. I have the fix and a new version, but the test machines,
and I suppose it will also be true of CRAN, are
I believe that this is because if it is outside of a function, then it
runs at INSTALL time, and codetools checks the installed code, i.e.
the function objects typically, and the checks never see the
globalVariables() call.
Gabor
On Tue, Sep 24, 2019 at 7:08 PM Henrik Bengtsson
wrote:
>
> 'R
'R CMD check' will give a warning that 'speed' is an unknown variable in:
low_speeds <- function(limit) {
subset(datasets::cars, speed <= limit)
}
We can tell 'R CMD check' that 'speed' is a false positive by
declaring it a "global" variable. This can be done, by:
low_speeds <-
> help(package="utils") shows the index, not utils-package.Rd.
Indeed, I should have run it before emailing, I meant:
package ? utils
which does show "utils-package.Rd" and similarly for other packages.
'help(topic)' shows a file which contains alias for 'topic'. In the case of
I would be in favour. I actually used R for several years before figuring
out that the vignette was usually where the useful introduction was. Until
then I was like “R help is way too technical”
On Tue, 24 Sep 2019 at 13:26, Joris Meys wrote:
> Dear Dr. Vichtbauer,
>
> I'm not a CRAN member,
It is worth noting that
help(package="")
shows file -package.Rd, while
help()
shows topic "package".
Topic -package.Rd is also printed at the top of the pdf manual, while
package.Rd follows the alphabetical ordering of the remaining topics. It is
unfortunate that Hadley Wickham's tools
Hi Dirk,
Point well taken, but the same goes for many other CRAN requirements. For
example, I can create totally useless help files for all the functions that
pass all checks. Just because some will try to skirt around a requirement
doesn't mean it's a useless requirement. In fact, the point
Wolfgang, Joris,
This may not necessarily work -- see "Goodhart's Law" [1]
Once you impose something like this, (some) will skirt it with just the
minimum requirement of an (essentially) empty file. An existing set of
examples is provided by the vignettes of (at least) one developer which
Dear Dr. Vichtbauer,
I'm not a CRAN member, but I personally think this is a sensible
requirement. I try to include those in every package myself, even if it's
only to direct people to a vignette.
That said, I do look for vignettes first when I encounter an unfamiliar
package actually. That
Hi All,
When starting to work with an unfamiliar package, one might typically look for
vignettes, a paper/book accompanying the package, a package website, and of
course the help files themselves, but
help(package="")
is often not so useful -- such a listing of functions (with titles) might
Hi,
I am uploading my R package to CRAN. One of the dynamic libraries the package
requires depends on LAPACKE library which usually integrated with BLAS and
CBLAS in the same .so file (as I understand). CRAN has OpenBLAS already
installed on the system. However, this OpenBLAS library does not
On 9/24/19 1:57 AM, Toby Hocking wrote:
Hi all,
is there a known fix for this WARNING which I am getting on solaris for my
newly submitted nc package?
https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/nc-00check.html
It seems that deparse() came across some non-printable
13 matches
Mail list logo
