I still hope to investigate using a hand-written wasm module as a library 
called from an Emscripten compiled program. To do this I will need to be able 
to get each to use the same malloc and wasmMemory. Will this change prevent 
such a thing from being done?

Regards

    -Mark

> On Sep 23, 2020, at 14:53, 'Sam Clegg' via emscripten-discuss 
> <[email protected]> wrote:
> 
> I recently made a change to start exporting the table from the WebAssembly 
> module:
> https://github.com/emscripten-core/emscripten/pull/12296 
> <https://github.com/emscripten-core/emscripten/pull/12296>
> 
> I'm hoping to followup with a similar change for the WebAssembly memory 
> (a.k.a `wasmMemory):
> https://github.com/emscripten-core/emscripten/issues/12315 
> <https://github.com/emscripten-core/emscripten/issues/12315>
> 
> If we go ahead with this change it will mean the WebAssembly module is in 
> charge of creating and exporting the memory rather than JavaScript.  One 
> potential downside here is that it removes the ability to adjust the memory 
> size and runtime, or supply your own memory (i.e. it removes the ability to 
> set `wasmMemory` or `INITIAL_MEMORY` on the Module object.
> 
> However there are many upsides to doing this:
> - Reduced JS size and complexity
> - Consistency with standalone more
> - WebAssembly is more self-contained
> - Easier to load and run emscripten-built WebAssembly modules in other 
> environments.
> 
> I'd like to found out how many developers out there are settings `wasmMemory` 
> or `INITIAL_MEMORY` at runtime to see how likely it is that we might be able 
> to make this switch.  Is possible of course that we could support both 
> modes.. although I would prefer not to.
> 

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/34853692-E256-4C4D-BC4D-F5AEAFAB7CD5%40callow.im.

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to