I don't know of one. But you could use save() to save the dataframe to a different file, then remove the dataframe from .GlobalEnv, then attach the different file. While not strictly speaking read-only, that should provide good protection against accidental changes to the dataframe in the normal course of things.
-Don At 6:13 AM -0800 1/11/08, Dan Kelley wrote: >QUESTION: is there a way to make objects (e.g. data frames) read-only? > >BACKGROUND: I am writing some functions that use a data frame (frequencies >of tidal constituents) that I want to be read-only. I can see how to >accomplish this within a single function (just define the data in the >function), but I'm not sure how to share read-only values between >(un-nested) functions. Is there a more elegant method than duplicating the >creation of the data frame in each function? > > >-- >View this message in context: >http://www.nabble.com/how-to-make-read-only-data-frames--tp14756183p14756183.html >Sent from the R help mailing list archive at Nabble.com. > >______________________________________________ >R-help@r-project.org mailing list >https://stat.ethz.ch/mailman/listinfo/r-help >PLEASE do read the posting guide http://www.R-project.org/posting-guide.html >and provide commented, minimal, self-contained, reproducible code. -- -------------------------------------- Don MacQueen Environmental Protection Department Lawrence Livermore National Laboratory Livermore, CA, USA 925-423-1062 ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.