connections (was [Rd] RFC: System and time support functions in R)

Prof Brian D Ripley
Tue, 25 Jul 2000 10:36:18 +0100 (BST)

On Tue, 25 Jul 2000, [iso-8859-1] Jens Oehlschlägel wrote:

> I agree it would be useful. Additionally I would vote for
> disentangling/extending some functionality in R.
> e.g. save() does not only creates an external representation, it also writes
> it to a file. So we cannot send the representation to a socket or just to a
> character variable. Same with load().
> e.g. scan() does combined physical read and parsing, i.e. it reads from file
> and keyboard, but not from a socket or character variable. Similarly write()
> and read.table(). The logic of how to convert character data too a dataframe
> should not be bound to file read.
> >From my point of view, a minimum solution would be generally allowing
> reading/writing from/to a character variable instead of file access. This
> would also allow filtering the data e.g. through a compression algorithm.

That's a different topic (from Duncan's and from my subject line).
The plan is to use the Svr4 idea of `connections' to replace files (and
scan does only read from files: stdin is a file to C).

Brian D. Ripley,        
Professor of Applied Statistics,
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272860 (secr)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595

r-devel mailing list -- Read
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: