Issue 44: return value handling odd
http://code.google.com/p/v8/issues/detail?id=44
Comment #4 by pete.gontier:
Thanks for #3, because that was my next question. This must be why the
parens are generally recommended for
evaluating JSON arriving via XHR. It seems this ought to be documented
so
Issue 44: return value handling odd
http://code.google.com/p/v8/issues/detail?id=44
Comment #3 by [EMAIL PROTECTED]:
I should add that you can have it evaluated as an expression by wrapping it
in
parenthesis: ({foo:12}).
--
You received this message because you are listed in the owner
or CC
Issue 44: return value handling odd
http://code.google.com/p/v8/issues/detail?id=44
Comment #2 by [EMAIL PROTECTED]:
When evaluating { foo: 12 } it is evaluated as a block of code with a
labeled
statement. Therefore, the result is 12 and not an object with a foo
property.
Similarly, { foo:12
Issue 44: return value handling odd
http://code.google.com/p/v8/issues/detail?id=44
Comment #1 by pete.gontier:
It seems arrays do work, or at least this one does:
[ 12,13,14 ]
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you st
Issue 44: return value handling odd
http://code.google.com/p/v8/issues/detail?id=44
New issue report by pete.gontier:
After invoking a script, I attempt to evaluate the return value. As
documented in the sample, returning a string works fine. However, I want to
return an object. If I write this s
