It requires an operating system.
On Wednesday, October 12, 2016 at 8:25:42 PM UTC-7, Bryce Peterson wrote:
>
> I have a very odd question. I've got a fairly powerful ARM board, similar
> to something like a Teensy or an MBED, with generous code-space and RAM.
>
> Theoretically, it should be enoug
I have a very odd question. I've got a fairly powerful ARM board, similar
to something like a Teensy or an MBED, with generous code-space and RAM.
Theoretically, it should be enough to run a JavaScript compiler, feeding it
js files from an SD card shield, but my question is... how would you do
I am attempting to build current "stable" version 5.3.332.45, which is not
the very latest (unstable) one.
So any recommendations, what do I need to do to compile it on CentOS 7 with
all recent updates using GCC?
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/grou
v8::External is exactly what I'm using - see the code snippet in the
original post.
The question was just referring to the ObjectTemplate used to generate the
object instances, on which I set the externals.
On Wed, Oct 12, 2016 at 9:18 AM, Jochen Eisinger
wrote:
> depends on what you mean by w
the stringification of a function doesn't get me back the entire source
though. That's what I need to send to chrome for debugging.
On Wednesday, October 12, 2016 at 12:17:20 AM UTC-7, Jochen Eisinger wrote:
>
> you can get the ScriptOrigin from a v8::Function via GetScriptOrigin. You
> can al
I assume that CentOS 7 doesn't have the required libraries to compile the
latest version of V8.
On Tue, Oct 11, 2016 at 4:19 PM Ivan Pizhenko
wrote:
> Tried this. I have following args.gn
>
> is_debug=true
> is_component_build=true
> target_cpu="x64"
> v8_target_cpu="x64"
> v8_postmortem_support
depends on what you mean by wrapper. Typically, we'd call a JS object that
corresponds to an embedder object a "wrapper"
On Wed, Oct 12, 2016 at 12:28 AM Zac Hansen wrote:
> why wouldn't you just use a v8::External? Isn't that exactly what they're
> meant for?
>
>
> On Monday, October 10, 2016
you can get the ScriptOrigin from a v8::Function via GetScriptOrigin. You
can also ToString a function to get the source, but you could as well
create a global to the source.
On Wed, Oct 12, 2016 at 12:49 AM Zac Hansen wrote:
> I'd like to keep around the data in a v8::ScriptCompiler::Source obj
