Another note for WIN XP:
Neither Chrome 49 or Firefox ESR 52.2.0 work with WebAssembly.
But the JS-flavour works.
Regards
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote
How: If you use Emscripten, then wasm support via a command-line flag will at first include and target the prototype polyfill. But as native wasm decoders appear in top engines (see the V8 native prototype decoder), Emscripten will auto-configure for best results. Another prototype: a JS AST compressor (encoder).
These prototypes will evolve and track draft specification changes as WebAssembly matures and receives progressively more developer testing. Other compilers than Emscripten, and other compiler frameworks than LLVM, will join the mix. I expect all engines will support fast native decoders. All these parts are means to the end of a common WebAssembly standard.
set Ide(imageDir) "TclApp"
Can you explain how it works? Is it an exe that combines tcl/tk and newlisp into one binary,Quote
Quote
> (setq Test 1)
1
> (inc 'Test)
2
> Test
1
> (inc Test)
2
> Test
2
Quote
.....This is by design, .mem files are created in optimized builds to reduce size and improve startup speed. You can disable them --memory-init-file 0 if you want, but it is not recommended. When they are emitted, they must be alongside the .js file so it can find it.