It's difficult to do by hand, but it's not too hard to automate - take
a look at https://github.com/hadley/roxygen3/blob/master/R/auto-imports.r.
It's part of roxygen3, but the code is relatively straighforward and
doesn't depend on much else in the package.
Hadley
On Sat, Sep 7, 2013 at 7:48 AM,
I also second Peter's proposal. I think that it is particularly helpful to
save time for maintainers of packages that were developed a longer time ago.
When writing new packages, it is relatively easy to keep track of which
functions from which packages need to be imported; when maintaining older
c
Well, it makes sense to me, since I have had the same issue.
Suppose you have two packages A and B. You would really like to import
both of them since it is too much work to figure out exactly which
functions you use, and you consider both of them fundamental to your own
work. So you would like
On 13-09-06 4:54 PM, Dr. Peter Ruckdeschel wrote:
Hi,
recently R CMD check --as-cran has noticed some more issues with
package namespace imports with the recommended remedy to
use importFrom() and friends.
In my case, there was only a conflict restricted to some few imports,
while I would prefe
Hi,
recently R CMD check --as-cran has noticed some more issues with
package namespace imports with the recommended remedy to
use importFrom() and friends.
In my case, there was only a conflict restricted to some few imports,
while I would prefer to still import all the non-conflicting objects,
m
