[R] "dump" Splus -> R

[Ross Ihaka]

Gregory R. Warnes writes:
 > 
 > Hi All,
 > 
 > I just used "dump" on Splus to transfer a pile of survival objects from
 > Splus 3.4 on Solaris 7 to R 0.63.3 on Intel. 
 > 
 > The only trick is that survival objects contain an element holding the
 > original call that generated the object.  When Splus writes these out, it
 > doesn't mark them in any way, so when R tries to read them in, it ends up
 > trying to reevaluate the call.  Not nice.  
 > 
 > Anyway, as all but one** of the offending calls occur in statements
 > that look like
 >    [...], call = func( param1, param2, [..] ), class = "myclass"
 > 
 > so I wrote the following perl script to encapsulate each call in 
 > as.call(expression(...)) :


I just tried dumping and sourcing/restoring an "lm" object under
Splus-3.4, it doesn't work there either!  This is very nasty indeed.

We can fix the problem in R by inserting quote() around call objects,
when we deparse, but what about Splus?

It seems like you may want to design your scripts to provide a
solution to the problem in both platforms.

	Ross
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-help-request at stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._