If you want to keep it as text, then you can just put it in the code: mydata <- '"","mpg","cyl","disp","hp","drat","wt","qsec","vs","am","gear","carb" "Mazda RX4",21,6,160,110,3.9,2.62,16.46,0,1,4,4 "Mazda RX4 Wag",21,6,160,110,3.9,2.875,17.02,0,1,4,4 "Datsun 710",22.8,4,108,93,3.85,2.32,18.61,1,1,4,1 '
and then you can read from it via text connections: read.csv(textConnection(mydata)) Gabor On Mon, Aug 4, 2014 at 12:11 PM, Keirstead, James E <j.keirst...@imperial.ac.uk> wrote: > I saw that, but actually I was wondering if there was a more general method. > I’d like to use plain text files if I can, instead of Rda files, since > they’re easier to maintain (and it’s a small file). > > On 4 Aug 2014, at 16:30, Jeroen Ooms <jeroen.o...@stat.ucla.edu> wrote: > >>> I’m developing a package and would like to include some data sets for >>> internal use only, e.g. configuration parameters for functions. What is >>> the preferred way of doing this? If I put them in data/, then R CMD check >>> asks me to document them but I’d prefer it if they floated beneath the >>> surface, without the users awareness. >> >> Perhaps in sysdata.rda. See "Writing R Extensions". > > ______________________________________________ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
