Re: [v8-users] BooleanObject::New(false) always returns true

Hmmm, this doesn't look right. There seems to be some API nonsense/bug, investigating... -- -- 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 unsubscribe

[v8-users] Compile V8 with mips64

Hi,guys. I tried to compile the v8 with mips64 on the loongson3a in release mode. And the result is the compile is ok, but when I run the v8's benchmark , such errors occurred: Richards: Error: Error during execution: queueCount = 149, holdCount = 59. DeltaBlue: ReferenceError: alert is not

Re: [v8-users] BooleanObject::New(false) always returns true

On Mon, Jul 29, 2013 at 9:41 AM, Sven Panne svenpa...@chromium.org wrote: Hmmm, this doesn't look right. There seems to be some API nonsense/bug, investigating... Actually things are correct, but very perplexing. Consider the following session in d8:

[v8-users] Re: BooleanObject::New(false) always returns true

So if i understand correctly, in order to obtain the underlying value of a BooleanObject, i need to first cast the Value to BooleanObject and then call BooleanValue() Do we need to perform the same casting from Value to NumberObject and StringObject to correctly obtain the underlying value ?

Re: [v8-users] Re: BooleanObject::New(false) always returns true

On Mon, Jul 29, 2013 at 2:13 PM, ioannis ioanni...@gmail.com wrote: So if i understand correctly, in order to obtain the underlying value of a BooleanObject, i need to first cast the Value to BooleanObject and then call BooleanValue() Yes, and this is caused by the fact that polymorphism