There's no ->/dereference operator in Persistent<> in 7.0, so maybe it was
removed for safety. (forcing it to be referenced from a local, and
therefore inside a handle scope)
I went from 5.5 to 7.0 without having to change any code here, but anywhere
I set the internal field is via a Local.
Ca
Figured it out, caused by the function being inlined, so can't be called.
On 2/9/2018 8:34 PM, Dickson Tan wrote:
Using dynamic libraries produces an identical error.
On Sunday, September 2, 2018 at 7:47:28 PM UTC+8, Dickson Tan wrote:
Hi,
I'm trying to use V8 v7.0 rc (pulled yesterd
Using dynamic libraries produces an identical error.
On Sunday, September 2, 2018 at 7:47:28 PM UTC+8, Dickson Tan wrote:
>
> Hi,
>
> I'm trying to use V8 v7.0 rc (pulled yesterday from git) from Rust, and
> some very basic calls work. However, when I try creating a new
> DeserializeInternalFiel
Hi,
I'm trying to use V8 v7.0 rc (pulled yesterday from git) from Rust, and
some very basic calls work. However, when I try creating a new
DeserializeInternalFieldsCallback to initialize a context, I get the
following linker error:
libv8-8489342a48c5ef6c.rlib(v8-8489342a48c5ef6c.2r60xiaen
memcpy(static_cast(buffer_->Data()) + bytes_used_,
data,bytes_to_save);
with this memcpy is it copying from data which is a const char pointer n
bytes_to_save into the array buffer_ or into a specific offset from the
array ?
--
--
v8-users mailing list
v8-users@googlegroups.com
http://group
