See https://tc39.github.io/ecma262/#sec-hasproperty vs.
https://tc39.github.io/ecma262/#sec-hasownproperty.
On Wed, Dec 7, 2016 at 2:48 PM, kent williams
wrote:
> If this is documented anywhere, I haven't found it.
>
> What is difference between v8::Object::Has() and
>
Just upgraded v8 from 4.6 to 5.3 and found a new behavior: garbage
collection can happen in a background thread after
ContextDisposedNotification and IdleNotificationDeadline return. My
idleNotificationDeadline runs in a loop with 1sec increments, and it
typically comes out after 1 or 2
I notice that v8 builds it's own ICU libraries.
Is it possible to suppress this and use the system versions?
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
If this is documented anywhere, I haven't found it.
What is difference between v8::Object::Has() and
v8::Object::HasOwnProperty()?
for example:
var x = { HasThisProperty : true };
Both functions return true.
What would be a case where one was true and the other false?
--
--
v8-users
I answered my own question again, sort of.
Both v8::Object::Has() and v8::Object::HasOwnProperty() will return true if
a property exists on an object.
On Wednesday, December 7, 2016 at 10:44:20 AM UTC-6, kent williams wrote:
>
> I should maybe try v8::Object::Has -- it looks like it will tell
OK so I solved this more or less.
1. The GN build is broken with respect to building static libraries. Once
you leave 'gn land' and try and build something you're kind of screwed.
2. The deprecated GYP build does the right thing. For the moment I don't
care if it's deprecated, since I'm going
On Wednesday, December 7, 2016 at 11:48:30 AM UTC-6, Ben Noordhuis wrote:
>
>
>
> The link order is fairly crucial. Try adding -Wl,--no-as-needed. If
> linking now succeeds, you know you need to rearrange the -l
> switches until it works.
Makes no difference. I can see why there's a
On Wed, Dec 7, 2016 at 6:31 PM, kent williams wrote:
>
> What I've done so far:
> Based on what I've gathered from the v8 WIKI combined with trial and error I
> use this script
>
> git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git
> export
I should maybe try v8::Object::Has -- it looks like it will tell you if an
object has a property, but it isn't really documented anywhere what it does.
On Wednesday, December 7, 2016 at 4:03:02 AM UTC-6, Jochen Eisinger wrote:
>
> You could use v8::Object::GetOwnPropertyNames instead of trying
Since I tried building with GN, I supplied arguments in the `gn args` txt
document. `target_os` was set to `android`, there is an explicit assertion
in BUILDCONFIG.gn however in /build/config that checks whether I am on a
linux or mac when targeting android. As far as I am aware building with GYP
What values do you give to -Dtarget_arch= ? , and how do you specify what
option do you use to specify the target os to gyp_v8
On Wednesday, December 7, 2016 at 1:50:53 PM UTC+2, Peter Kanev wrote:
>
> I work on a project that embeds v8 in native Android applications, the v8
> used for all 3
I work on a project that embeds v8 in native Android applications, the v8
used for all 3 architectures (arm v7, arm 64, x86) we support is built on
Linux machines.
As a next step the project must support generation of snapshot blobs for
those 3 archs, and as such I need to build the
Hey, do let me know if you succeed in building for android OS under
Windows. I just tried with GN and cross-compiling and building for android
seems impossible at the moment. Errors are thrown in your face as early as
the configuration phase (gn args)
On Wednesday, December 7, 2016 at 12:09:53
Well i already figured out how to build on windows so i feel comitted to
gyp :) . However do you know the option to specify os that i want to build
for , and do you know what values take -Dtarget_arch= i want to build for
arm and arm64 and atom32 for android
On Wednesday, December 7, 2016 at
You could use v8::Object::GetOwnPropertyNames instead of trying each key
individually
On Tue, Dec 6, 2016 at 11:04 PM kent williams
wrote:
> There's a convention that we use for our C++ native functions called from
> C++, where required arguments are followed
no, the options aren't documented :-/
However, gyp is deprecated, have you looked at gn yet?
On Wed, Dec 7, 2016 at 9:30 AM wrote:
> Is there anywhere documented what options and values does gypfiles/gyp_v8
> script take ?
>
> --
> --
> v8-users mailing list
>
Is there anywhere documented what options and values does gypfiles/gyp_v8
script take ?
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" group.
To
17 matches
Mail list logo