Re: [Rd] A doubt about substitute() after delayedAssign()

2012-05-01 Thread Duncan Murdoch
On 12-05-01 4:21 PM, Philippe Grosjean wrote: On 29/04/12 13:50, Duncan Murdoch wrote: On 12-04-29 3:30 AM, Philippe Grosjean wrote: > Hello, > > ?delayedAssign presents substitute() as a way to look at the expression > in the promise. However, > > msg<- "old" > delayedAssign(

Re: [Rd] A doubt about substitute() after delayedAssign()

2012-05-01 Thread Philippe Grosjean
On 29/04/12 13:50, Duncan Murdoch wrote: On 12-04-29 3:30 AM, Philippe Grosjean wrote: > Hello, > > ?delayedAssign presents substitute() as a way to look at the expression > in the promise. However, > > msg<- "old" > delayedAssign("x", msg) > msg<- "new!" > x #- new! > substitute(x) #-

Re: [Rd] A doubt about substitute() after delayedAssign()

2012-04-29 Thread Duncan Murdoch
On 12-04-29 3:30 AM, Philippe Grosjean wrote: > Hello, > > ?delayedAssign presents substitute() as a way to look at the expression > in the promise. However, > > msg<- "old" > delayedAssign("x", msg) > msg<- "new!" > x #- new! > substitute(x) #- x (was 'msg' ?) > > Here, we just got 'x'... shouldn

[Rd] A doubt about substitute() after delayedAssign()

2012-04-29 Thread Philippe Grosjean
Hello, ?delayedAssign presents substitute() as a way to look at the expression in the promise. However, msg <- "old" delayedAssign("x", msg) msg <- "new!" x #- new! substitute(x) #- x (was 'msg' ?) Here, we just got 'x'... shouldn't we got 'msg'? Same result when the promise is not evaluated