Re: [v8-users] Re: Why env1 can't access the env2 global variables

2014-11-13 Thread Louis Santillan
My inclination is that your v8::Isolate::GetCurrent() call in v8_str is the culprit. So while you created two contexts, you used one isolate. On Thu, Nov 13, 2014 at 8:00 PM, Tom Fan wrote: > Context::Scope don't destroy context, it just help you enter/exit context > when code enter/leave c++ sc

[v8-users] Re: Why env1 can't access the env2 global variables

2014-11-13 Thread Tom Fan
Context::Scope don't destroy context, it just help you enter/exit context when code enter/leave c++ scope automatically. I wanna env1 and evn2 share global object, but i can't access evn1's global variable p which i set it at evn1 before. On Friday, November 14, 2014 11:45:52 AM UTC+8, Flying

[v8-users] Re: Why env1 can't access the env2 global variables

2014-11-13 Thread Flying Jester
It looks really suspicious to me that you are creating contexts and context scopes and then immediately destroying them like that. For what you are doing, you need at most one context scope and one context. Create them at the very beginning, and destroy them at the very end. On Thursday, Nove