Thanks, all, for your quick and comprehensive help with this - very much
appreciated in my R journey.
Leslie
On Tue, Aug 30, 2016 at 8:03 PM, Jeff Newmiller
wrote:
> Thanks for the perspective, Martin. I personally feel like attaching to
> the search path is more confusing than being explicit,
Thanks for the perspective, Martin. I personally feel like attaching to the
search path is more confusing than being explicit, because it appears
indistinguishable from namespace pollution yet for modifying data it creates
copies in the current environment (in-place editing requires `<<-` which
> Jeff Newmiller
> on Tue, 30 Aug 2016 09:36:05 -0700 writes:
> You cannot. However, you can load the file into a dedicated environment
to keep those names separated from your global environment. e.g. [1]
yes, that's my "famous" only-allowed use of attach() :
attach() an rda-f
You cannot. However, you can load the file into a dedicated environment to keep
those names separated from your global environment. e.g. [1]
The saveRDS/loadRDS functions are an alternative handle one object at a time
without dragging the object names into the picture (you have to name the
re-l
I think that the .rda extension is the old extension convention for what
now gets the .RData extension name by convention.
These are basically workspaces. These .RData files can contain multiple
data objects, and all objects seem to read back in with the same name
that they were saved with usi
Hi,
I'm slowly migrating from SAS to R and - for the very first time - I'm
working with a native .Rda data file (rather than importing data from other
sources). When I load this .Rda file into the global environment using
load("file path") I see a data.frame in the global environment called
"mydat
6 matches
Mail list logo
