Re: [R] evaluation revisited

Gabor Grothendieck wrote: > On Wed, Jan 28, 2009 at 6:26 AM, Wacek Kusnierczyk > wrote: > >> Gabor Grothendieck wrote: >> >>> The argument to eval.parent is evaluated before eval.parent >>> ever sees it. >>> >> really? eval.parent is just a regular r function, a wrapper for eval >>

Re: [R] evaluation revisited

On Wed, Jan 28, 2009 at 6:26 AM, Wacek Kusnierczyk wrote: > Gabor Grothendieck wrote: >> The argument to eval.parent is evaluated before eval.parent >> ever sees it. > > really? eval.parent is just a regular r function, a wrapper for eval > with envir=parent.frame(). the arguments to eval.parent

Re: [R] evaluation revisited

Wacek Kusnierczyk wrote: > Gabor Grothendieck wrote: > >> The argument to eval.parent is evaluated before eval.parent >> ever sees it. >> > > really? eval.parent is just a regular r function, a wrapper for eval > with envir=parent.frame(). the arguments to eval.parent are passed to > eva

Re: [R] evaluation revisited

Gabor Grothendieck wrote: > The argument to eval.parent is evaluated before eval.parent > ever sees it. really? eval.parent is just a regular r function, a wrapper for eval with envir=parent.frame(). the arguments to eval.parent are passed to eval *unevaluated* (as promises), and are only evalu

Re: [R] evaluation revisited

The argument to eval.parent is evaluated before eval.parent ever sees it. Try issuing this command before you run your code: debug(eval.parent) and look at the value of the arguments as passed to eval.parent in the debugger. On Wed, Jan 28, 2009 at 2:29 AM, wrote: > I'm still going over old e

[R] evaluation revisited

I'm still going over old emails and trying to get my head around evaluation so I'm persistent if nothing else. A while back , an expert sent me below as an exercise in understanding and I only got around to it tonight. I understand some of the output but not all of it and I put "Why not Zero