Hi Shaukat,

I'd like to "ditto" your comments -- I faced the same problem with 
interceptors last year and it sounds like not much has improved since then. 
 I was forced to abandon my project because "the V8 source is the 
documentation".  V8 user's time should be spent on their projects, it makes 
no sense for every V8 user to reverse engineer V8 because the people who 
work on V8 full time don't want or need documentation.  When functionality 
is non-trivial, lack of documentation quickly devolves into a show-stopper.

For what it's worth, Harmony proxies are working in V8 and most of the 
accessor/interceptor functionality can now be used though the JS code 
itself.  Proxies are documented in the ES6 draft spec, so there is 
documentation to work from.

                      -J



On Tuesday, January 13, 2015 at 2:22:03 AM UTC-8, Shaukat Mahmood Ahmad 
wrote:
>
> It seems Google's official documentation at (
> https://developers.google.com/v8/embed) is outdated and is not compatible 
> with available release of v8 source repository.
>
> Examples are Accessors and Interceptors sections where the presented 
> examples, APIs and classes are neither directly exposed to V8 embedder via 
> (include/v8.h) nor the APIs are compatible with latest available 
> implementation of V8, following are the examples or poor, bad and incorrect 
> sample code presented in google's offical documentation.
>
> Local<Value> XGetter(Local<String> property,
>                         const AccessorInfo& info) {
>     return Integer::New(x);
>   }
>
>   void XSetter(Local<String> property, Local<Value> value,
>                const AccessorInfo& info) {
>     x = value->Int32Value();
>   }
>
>   // YGetter/YSetter are so similar they are omitted for brevity
>
>   Local<ObjectTemplate> global_templ = ObjectTemplate::New();
>   global_templ->SetAccessor(String::New("x"), XGetter, XSetter);
>   global_templ->SetAccessor(String::New("y"), YGetter, YSetter);
>   Persistent<Context> context = Context::New(NULL, global_templ);
>
> It is really disappointing and discouraging for developers who are 
> interested to adopt V8 for their applications and it seems like team google 
> is not interested in external users of V8 and they are developing this 
> library for their own specific needs without taking any care for backward 
> compatibility and documentation updates. 
>
>
>
>
>
>
>
>
>
>
>

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to