Thanks everyone. That makes sense, since these variables are "block
scoped", so having them available outside the scope wouldn't work.
Cheers,
Ian
On Tuesday, 4 April 2017 00:08:27 UTC-7, Ben Noordhuis wrote:
>
> On Tue, Apr 4, 2017 at 5:02 AM, Ian Bull
> wrote:
> > Can we
Yes, just to confirm:
Starting without snapshot, especially in Debug mode, has become much
slower, because more work is being done there (mostly compilation of
builtins and bytecode handlers).
This is working as intended. I.e. it's not considered a bug/problem, will
not be improved over time, in
from the docs:
http://v8.paulfryzel.com/docs/master/namespacev8.html#ac135beae5f0c8b290255accb438f990e
Returns a non-empty handle if the interceptor intercepts the request
so make sure you are returning an empty handle for properties your object
shouldn't respond to.
On Tue, Apr 4, 2017 at
I just implemented all the callbacks, and I see that for "with" there are
calls to QueryProperty, which are not present in the no-with scenario.
Maybe I can take it from there. Thanks for the idea!
On Tuesday, April 4, 2017 at 9:05:11 AM UTC+3, Zac Hansen wrote:
>
> I don't know for sure, but if
you can tell the linker to not care about order.. but presumably it's
faster if you put them in the right order to begin with.
On Thursday, March 30, 2017 at 5:47:12 AM UTC-7, Nicolò Cavalleri wrote:
>
> Actually the problem was that I forgot to use circular dependencies, as
> it's almost the
do you have it working if you connect with chrome then refresh chrome that
it works?
When I reconnect to the same embedded v8 app, I get a slightly different
set of messages that don't properly set up the debugger the second time.
Thanks.
On Thursday, March 23, 2017 at 9:32:15 AM UTC-7,
I don't know for sure, but if you don't tell the interceptor that a isn't a
property on CONS, then it thinks it is and then it finds cons_object.a but
then you don't have a value for it, so it returns undefined.
Have you fully implemented all 5 of the callbacks for setnamedpropertyhandler?
maybe
Yes, I use SetNamedPropertyHandler. However, I'd like to make the following
distinction:
If I am *not* inside "using", the handler for "a" should return
v8::Undefined (or some other preset value).
If I *am* inside "using", the handler should not return anything at all,
and let V8 determine the