https://docs.google.com/document/d/1AT5-T0aHGp7Lt29vPWFr2-qG8r3l9CByyvKwEuA8Ec0/edit?usp=sharing
is now complete, including sections on technical design, security
considerations, and alternatives considered that were missing yesterday when I
sent the previous message. Comments appreciated!
--
Due to the pathological API changes in V8, you are going to have a ton of
headaches if you try to use any prepackaged version. You would save
yourself tons of trouble to just compile it yourself, rather than using a
package manager's version. Well, that's tons of trouble, too. But it will
be le
Vl8uyu67yyhhnbc ,zero3etttyg5e4r9e0
4Pjftj8a[
On May 18, 2015 7:36 PM, "Sven Panne" wrote:
> On Tue, May 12, 2015 at 6:11 PM, Jason Josephy wrote:
>
>> I just built using Visual Studio and I am confused by the generated libs.
>> I read there should be a v8_lib.lib that I can link to but I see t
Hi Toon,
the second solution worked perfectly, thanks!
While with the first in the few quick tests I've made it looks that the
nested scope can see only a clone of the parent global and any subsequent
change happened to the parent global was not seed by the child.
Alberto
Il giorno mercoledì
If you get V8 as https://developers.google.com/v8/build describes, and
embed it like in the example at https://developers.google.com/v8/get_started,
then everything should just work.
Of course you're free to choose a different local directory structure, but
then it's up to you to fiddle with paths
