Re: [v8-users] Implication of the context parameter in v8::Object::Set().

Another major reason is that property access is checked. If you're e.g., trying to set a property on a "window" of an iframe you're not supposed to have access to from the passed in context (other iframe), this won't be allowed. On Wed, Jan 18, 2017 at 8:24 AM Jochen Eisinger

Re: [v8-users] Implication of the context parameter in v8::Object::Set().

right. also, it makes it explicit in which context a possible exception should be thrown On Wed, Jan 18, 2017 at 8:19 AM Ben Noordhuis wrote: > On Tue, Jan 17, 2017 at 9:03 PM, Jane Chen wrote: > > Why does v8::Object::Set() takes a context parameter

Re: [v8-users] Implication of the context parameter in v8::Object::Set().

On Tue, Jan 17, 2017 at 9:03 PM, Jane Chen wrote: > Why does v8::Object::Set() takes a context parameter now? Does it mean that > if an object is created in one context, it can only be used in that context? > > Thanks. The rules for object and property access didn't change.

[v8-users] Implication of the context parameter in v8::Object::Set().

Why does v8::Object::Set() takes a context parameter now? Does it mean that if an object is created in one context, it can only be used in that context? Thanks. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message