From rh at knut-krueger.de  Thu May  8 08:59:43 2014
From: rh at knut-krueger.de (Knut Krueger)
Date: Thu, 08 May 2014 08:59:43 +0200
Subject: [Rd] checking dependencies in R code ... WARNING
In-Reply-To: <1877523548.47233.1399530949612.JavaMail.zimbra@openanalytics.eu>
References: <536B20E7.3080103@knut-krueger.de>
	<1877523548.47233.1399530949612.JavaMail.zimbra@openanalytics.eu>
Message-ID: <536B2B5F.40809@knut-krueger.de>

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.
>
> See
>
> http://cran.r-project.org/doc/manuals/R-exts.html#Package-Dependencies
>
> Best,
> Tobias

Hi Tobias,

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,

DESCRIPTION
Imports: utils, foo, ...

it is included

NAMESAPCE:
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.


Best
Knut



[Rd] checking dependencies in R code ... WARNING
Knut Krueger