Indeed there are, after a fashion. I'm not sure if any of them are really all that useful, though. R::Writer is marked a alpha code, so with all due respect there's no way I'd use that (yet) for our lab's data analysis. FWIW, I'm also not sure if I'd personally have much use for the R::Writer approach; if one can already write flexible R code, why get perl to do it for you?

The RSPerl module did work a couple of years ago (although not perfectly, even back then) and changes to R in the meantime have apparently broken the module (which appears to be unmaintained). I've toyed with trying to work on the RSPerl module myself, but my lack of knowledge of perl internals has so far put me off. Maybe some day...

Instead, my approach in the past has generally been to either maintain R code in separate scripts (and R libraries for the larger stuff), and to pass data via temporary files and system() calls to Rscript. Certainly it's ugly, but at least it's relatively reliable and easily hidden behind a convenient perl wrapper.

Tim

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.