>> Can write.table and read.table really be so asymmetric? > > write() is a wrapper for cat() and read() is a wrapper for scan() so the > question should really be can cat() and scan() be so asymmetric. Looking at > their help pages, I would say that at least some degree of asymmetry is > plausible. Perhaps using save() with load() , or dput() with dget(), which > are pairings that promise to have symmetry?
Why should I have to care about the internal implementation details? This is one of the things that really frustrates me (and other new users of R) - read.table/write.table and read.csv/write.csv are named symmetrically, but do not work symmetrically. Hadley -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://had.co.nz/ ______________________________________________ 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.
