Comment #1 on issue 1022 by cmarcelo: Interceptor "blocking" setter in
prototype
http://code.google.com/p/v8/issues/detail?id=1022
I have tried to read some code related to setting and getting properties.
I've found something that might be interesting.
There's a function JSObject::GetPropertyPostInterceptor(), it is called
after a get property happens and we hit the InstanceTemplate's interceptor
and it returns empty handle. This function does two things
- first check for local property (ignoring the interceptor);
- if not found, then get the prototype and search again there.
On the other hand, in the setting execution, in
JSObject::SetPropertyPostInterceptor, seems to be called in a very similar
situation, but does like this
- check for local property (ignoring the interceptor);
- if not found, then create a new local property with AddProperty.
At this point I was expecting that if not found, the search (for
setters/interceptors, not locals in this case) would continue in the
prototype chain. Does it make sense?
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
