Many thanks for the info.
I see the point but I'll think calling the spData would be a cheaper
price to pay. If each package one load provide access to their variables
things are likely to get messy.
I guess many R users would like to control the variables in their global
environment.
And
This is intended/expected because the spdep package *depends* on the
spData package (see https://cran.r-project.org/web/packages/spdep/),
which means that the maintainer of spdep intends also spData to be
*attached* whenever spdep is attached.If they would have only
imported it, then spData
Helllo,
Thanks for the info. I still think these variables should not be loaded
when library(spdep) is called.
But I'll handle it following your suggestion.
Thanks,
Jeremie
> It turns out that that 'x' comes from the spData package and lives
> inside that package (part of its
It turns out that that 'x' comes from the spData package and lives
inside that package (part of its namespace).
> spData::x
[1] 0 30 60 90 120 150 180 210 240 270 300 330 360 390 420 450
This is conceptually no different from other objects in package
namespace, although we are more used to
Hello,
I found a dangerous issue in the library spdep. I get variables x and y
that cannot be removed by rm() and I don't don't how they show up. Can
anyone reproduce this?
~$ R --vanilla
> rm(list=ls())
> library(spdep)
> x
[1] 0 30 60 90 120 150 180 210 240 270 300 330 360 390 420 450
5 matches
Mail list logo
