On 16 August 2017 at 09:44, Duncan Murdoch wrote:
| On 16/08/2017 8:31 AM, Dirk Eddelbuettel wrote:
| >
| > On 16 August 2017 at 12:51, peter dalgaard wrote:
| > | > On 16 Aug 2017, at 11:11 , Berry Boessenkool
wrote:
| > | >
| > | > if a function in a package uses graphics::legend in the code,
On 16/08/2017 8:31 AM, Dirk Eddelbuettel wrote:
On 16 August 2017 at 12:51, peter dalgaard wrote:
| > On 16 Aug 2017, at 11:11 , Berry Boessenkool
wrote:
| >
| > if a function in a package uses graphics::legend in the code, but does not
import it in the namespace, shouldn't there be a warning
On 16 August 2017 at 12:51, peter dalgaard wrote:
| > On 16 Aug 2017, at 11:11 , Berry Boessenkool
wrote:
| >
| > if a function in a package uses graphics::legend in the code, but does not
import it in the namespace, shouldn't there be a warning in the check?
| >
|
| Er, no... Importing into
> On 16 Aug 2017, at 11:11 , Berry Boessenkool
> wrote:
>
>
> Hi,
>
>
> if a function in a package uses graphics::legend in the code, but does not
> import it in the namespace, shouldn't there be a warning in the check?
>
Er, no... Importing into a namespace is used to avoid the graphics:
On 16 August 2017 at 09:11, Berry Boessenkool wrote:
| if a function in a package uses graphics::legend in the code, but does not
import it in the namespace, shouldn't there be a warning in the check?
The 'graphics' package is a base package, and as such *always* available
where R is -- see its
