Re: [Rd] R-3.3.3/R-3.4.0 change in sys.call(sys.parent())

On Thu, May 11, 2017 at 8:03 PM, William Dunlap wrote: > Here is a case where the current scheme fails: > > > with(datasets::mtcars, xyplot(mpg~wt|gear)$call) > xyplot(substitute(expr), data, enclos = parent.frame()) Right, thanks. So I guess I can't avoid setting $call

Re: [Rd] R-3.3.3/R-3.4.0 change in sys.call(sys.parent())

Here is a case where the current scheme fails: > with(datasets::mtcars, xyplot(mpg~wt|gear)$call) xyplot(substitute(expr), data, enclos = parent.frame()) Bill Dunlap TIBCO Software wdunlap tibco.com On Thu, May 11, 2017 at 1:09 AM, Deepayan Sarkar wrote: > On

Re: [Rd] R-3.3.3/R-3.4.0 change in sys.call(sys.parent())

On Wed, May 10, 2017 at 2:36 AM, William Dunlap via R-devel wrote: > Some formula methods for S3 generic functions use the idiom > returnValue$call <- sys.call(sys.parent()) > to show how to recreate the returned object or to use as a label on a > plot. It is often

Re: [Rd] R-3.3.3/R-3.4.0 change in sys.call(sys.parent())

The difference in the outputs between 3.3 and 3.4 is in how call expressions are selected in presence of .Internals. R is asked for a call expression for "eval". In 3.3 one gets the arguments for the call expression from the .Internal that implements eval. In 3.4 one gets the arguments for