ҪҸ
bytecode needs runtime to execute indeed. that runtime is interpreter
Size: a a a
2019 July 17
ҪҸ
the result is not c code as @voronovm showed above. so I’m not sure that I understand you correctly
P
this is the original post
P
bytecode needs runtime to execute indeed. that runtime is interpreter
that's relative
P
bytecode doesn't imply interpreter
P
bytecode can be a JIT, interpeter or VM
P
the definition is diffuse
MV
It is excatly how an interpreter loop should look like
P
It is excatly how an interpreter loop should look like
well, then I retract myself
P
I couldn't see the whole code yet
MV
Anyway, quickjs seems like a good start
P
you can try the benchmarks
P
at least trying to beat v8 is something
ҪҸ
not sure tht V8 and quick.js are comparable things
MV
quickjs is interpreter, v8 has JIT and really they are uncomparable by speed (interpreters could bit such good jit only on some special cases, not generic)
ҪҸ
anyway I think we are bit off-topic :)
で
> Can compile Javascript sources to executables with no external dependency.
that means that it compiles to bytecode + interpreter and not c
that means that it compiles to bytecode + interpreter and not c
I think it just adds bytecode to own binary like sfx archive