« Why Big Data? Learning Curves | Main | R User Groups Highlight R Creativity »

September 30, 2015


Feed You can follow this conversation by subscribing to the comment feed for this post.

Just FYI - that isn't at all what repr does.

When you embed R inside another language or whatever, you need a way to talk to R and get results back. Usually the way you do that is by opening a network socket (on the same machine) from R to whatever it's talking to. That's how Jupyter works too. So you tell R to do things by writing commands to the socket and then sending the "enter" code (im simpifying). But how do you get the result back?

If the result from R is just some text it's easy you can just read from the socket.

If its anything else, it has to be converted into a byte representation so it can be sent through the socket and decoded.

That's what repr does. It's not a graphics device. It's a way of encoding non-textual R data in a form that can be transmitted through a socket and decoded.

The comments to this entry are closed.

Search Revolutions Blog

Got comments or suggestions for the blog editor?
Email David Smith.
Follow revodavid on Twitter Follow David on Twitter: @revodavid
Get this blog via email with Blogtrottr