[Rd] checking dependencies in R code ... WARNING
rh at knut-krueger.de
Thu May 8 08:59:43 CEST 2014
Am 08.05.2014 08:35, schrieb Tobias Verbeke:
> Hi Knut,
> The code will contain library or require statements, which
> do not belong there, but need to replaced by specifying the
> dependencies on these packages in the DESCRIPTION file
> (Depends / Imports field). For imports you also need to
> make sure the NAMESPACE file contains the intended statements.
if I am right it should be a code from the utils package
# Use the internal win32consoleCompletion function in utils package
res <- utils:::.win32consoleCompletion(code, nchar(code))
IMPORT field ... Namespaces accessed by the ‘::’ and ‘:::’ operators
must be listed here,
Imports: utils, foo, ...
it is included
import(utils, foo, ....)
could it be another problem? I found:
Using foo:::f instead of foo::f allows access to unexported objects.
This is generally not recommended, as the semantics of unexported
objects may be changed by the package author in routine maintenance.
More information about the R-devel