at lines 651 & 653 (integer_binary function):
if (code == DIVOP || code == POWOP)
ans = allocVector(REALSXP, n);
else
ans = allocVector(INTSXP, n);
There are calls to warningcall() later in the function, which can
trigger garbbage collection.
Looks like the typical scena
Jonathan,
All exported functions must have documentation entries to pass R CMD check
without warnings.
Functions within your package do not need another function in your package
to be exported to call it without :::, but code not in your package (ie
functions in other packages or user code) do.
I think part of this may be my (possibly flawed) understanding of
documentation requirements for CRAN -- if a function is exported to
the namespace, does CRAN require documentation of that function? The
reason I ask is that I have a lot of these little functions that have
no need for documentation
On 13-07-12 5:52 PM, Jonathan Greenberg wrote:
R-developers:
I'm working on updating my R package "spatial.tools", and one thing I
was wondering was the proper way to have hidden functions -- should I
simply not export them to the namespace and use the ::: operator to
call them (which is what I
R-developers:
I'm working on updating my R package "spatial.tools", and one thing I
was wondering was the proper way to have hidden functions -- should I
simply not export them to the namespace and use the ::: operator to
call them (which is what I currently do)?
--j
--
Jonathan A. Greenberg, Ph
