diff options
| author | Derek Schuff <dschuff@chromium.org> | 2015-08-26 11:21:47 -0700 |
|---|---|---|
| committer | Derek Schuff <dschuff@chromium.org> | 2015-08-26 11:21:47 -0700 |
| commit | 66605f678b59ecad6fcb2f883e1ddfea7969dba8 (patch) | |
| tree | 8df207ff01d20d2815e58bab534e44445feedc7f /Modules.md | |
| parent | 773dca0adefcdd44e6cbced6507822c1bfdb94d8 (diff) | |
| download | nanowasm-design-66605f678b59ecad6fcb2f883e1ddfea7969dba8.tar.gz | |
Factor dynamic linking section into its own file
Fix up some references about dynamic linking and move it to its own file, since
it will be expanding soon and referring to a fair number of other sections.
Also add a little extra motivation to the introductory text.
Diffstat (limited to 'Modules.md')
| -rw-r--r-- | Modules.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -102,7 +102,7 @@ scope of "all" is a nuanced question), a single app using multiple independent libraries would have to hope that all the WebAssembly modules transitively used by those libraries "played well" together (e.g., explicitly shared `malloc` and coordinated global address ranges). Instead, the -[dynamic linking future feature](FutureFeatures.md#dynamic-linking) is intended +[dynamic linking future feature](DynamicLinking.md) is intended to allow *explicitly* sharing linear memory between multiple modules. ## Initial state of linear memory |
