Re: [v8-users] Current value in interceptors

2016-06-27 Thread Ben Noordhuis
On Mon, Jun 27, 2016 at 3:20 PM, Danny Dorfman wrote: > Hello Ben, > Actually, I was expecting the current value to be there. As Jochen mentioned > below, it's only valid if it's been previously set within the interceptor. > Is there a way to know the real current value

Re: [v8-users] Current value in interceptors

2016-06-27 Thread Danny Dorfman
Hello Ben, Actually, I was expecting the current value to be there. As Jochen mentioned below, it's only valid if it's been previously set within the interceptor. Is there a way to know the *real* current value before it's overwritten? D. On Monday, June 27, 2016 at 12:24:57 PM UTC+3, Ben

Re: [v8-users] Current value in interceptors

2016-06-27 Thread Jochen Eisinger
ReturnValue::Get only tells you what the return value you previously have set is. Ideally, you use a non-masking interceptor. In that case, you know that the current value is not defined. best -jochen On Mon, Jun 27, 2016 at 11:24 AM Ben Noordhuis wrote: > On Sun, Jun 26,

Re: [v8-users] Current value in interceptors

2016-06-27 Thread Ben Noordhuis
On Sun, Jun 26, 2016 at 3:04 PM, Danny Dorfman wrote: > Hi there, > > I am writing some interceptor code for my objects, and I was wondering, > whether it was possible to know, > what is the current value for the property, before it's overwritten by >

[v8-users] Current value in interceptors

2016-06-26 Thread Danny Dorfman
Hi there, I am writing some interceptor code for my objects, and I was wondering, whether it was possible to know, what is the *current* value for the property, before it's overwritten by args.GetReturnValue().*Set*(whatever). I need something like args.GetReturnValue().*Get*(), but there is