Here's an interesting fact about ExternalStringResource::data(). Its current
contract actually requires the embedder to keep the returned char array
pointer
alive until the resource is destructed. It means that the pointer can be
cached
in the C++ resource object at a known offset and accessed from our generated
code. Of course, it makes the resource object one word larger, but similar
to
this patch it can save a lot of runtime calls. Have you considered this
approach?
-- Vitaly
http://codereview.chromium.org/8568013/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
