From 21c6c37f01c69e5c0e49ec7cb66489fffca1a1fb Mon Sep 17 00:00:00 2001 From: JF Bastien Date: Tue, 15 Mar 2016 10:49:27 -0700 Subject: Mention limited dynamic linking Further clarifications will be needed to explain the Wasm object's API. That should be done in a separate PR. --- DynamicLinking.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'DynamicLinking.md') diff --git a/DynamicLinking.md b/DynamicLinking.md index f110d8f..09a0a89 100644 --- a/DynamicLinking.md +++ b/DynamicLinking.md @@ -2,10 +2,13 @@ Dynamic loading of code is in [the MVP](MVP.md) in the form of [modules](Modules.md), but all loaded modules have their own separate -[linear memory](AstSemantics.md#linear-memory) and cannot share -[function pointers](AstSemantics.md#calls). Dynamic linking will allow -developers to share memory and function pointers between WebAssembly -dynamic libraries. +[linear memory](AstSemantics.md#linear-memory) by default and cannot share +[function pointers](AstSemantics.md#calls). Limited collaboration between +modules is possible im the MVP by having two modules share the same linear +memory and invoke each other through the embedder. + +True dynamic linking will allow developers to share memory *and* function +pointers between WebAssembly dynamic libraries. WebAssembly will support both load-time and run-time (`dlopen`) dynamic linking of libraries. -- cgit v1.2.3