Yes, and emterpreter and proxy-to-worker should as well. Bugs are always possible of course ;) but in principle these are orthogonal, separate issues: wasm replaces our asm.js compiled code, while those other features do not directly impact compiled code (well, emterpreter does in a sense, but it's just different compiled code).
On Sat, Feb 11, 2017 at 3:07 AM, Floh <[email protected]> wrote: > I'm not using the Emterpreter or proxy-to-worker (no workers at all in > fact), but most of the HTML5 APIs in my demos. So far everything worked out > of the box (the wasm link under the screenshots points to the WebAssembly > versions: http://floooh.github.io/oryol-samples/) > > Cheers, > -Floh. > > > Am Samstag, 11. Februar 2017 10:31:16 UTC+1 schrieb awt: >> >> Hi, >> >> I am currently using Emscripten features like Emterpreter and >> proxy-to-worker. I might use WebGL in the future although I'm using >> Canvas2D now. Will all these work seamlessly with Webassembly when compiled >> with Emscripten? >> > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
