Just one thing to add to Jason's very helpful posting and
explanations:
Jason == Jason Turner [EMAIL PROTECTED]
on Sat, 04 Oct 2003 07:30:03 +1200 writes:
.
.
Jason Short answer: anything that's R code *should* be
Jason named with .R at the end.
Dear All,
thanks for your clarifications. When I said that my .RData files load
fines, I should have added that the files are images that contain
objetcs, not code. In the bad ol' days under the thrall of the dark
ruler (W2K), I would write all my code in text files, saved as foo.txt,
and then
Federico Calboli [EMAIL PROTECTED] writes:
Dear All,
I suspect this is kind of dumb, but when I was under the thrall of the
dark lord (read, using a W2K box), all my work in R files came out as
foo.RData. I moved on to GNU/Linux, and all the old .RData files keep on
working as they used.
*.R is for the script file and is ASCII type.
*.Rdata (or sometimes *.rda) is the usual extension for R data and
contains binary information.
If you try to cat a *.Rdata file, you will end up with gibberish as it
is binary.
Try opening *.Rdata with emacs if you can. Emacs will recognise it as a
On Fri, 2003-10-03 at 13:16, Adaikalavan RAMASAMY wrote:
*.R is for the script file and is ASCII type.
*.Rdata (or sometimes *.rda) is the usual extension for R data and
contains binary information.
If you try to cat a *.Rdata file, you will end up with gibberish as it
is binary.
Try
Federico Calboli wrote:
On Fri, 2003-10-03 at 13:16, Adaikalavan RAMASAMY wrote:
*.R is for the script file and is ASCII type.
*.Rdata (or sometimes *.rda) is the usual extension for R data and
contains binary information.
If you try to cat a *.Rdata file, you will end up with gibberish as it
is
