diff options
| author | Derek Schuff <dschuff@chromium.org> | 2015-08-26 14:42:18 -0700 |
|---|---|---|
| committer | Derek Schuff <dschuff@chromium.org> | 2015-08-26 14:42:18 -0700 |
| commit | ce509cdb9ec33fc439e389c82dffc1e641c1925d (patch) | |
| tree | 7f7884596f2e5ea90297ad7279ab86272025a113 /Modules.md | |
| parent | 773dca0adefcdd44e6cbced6507822c1bfdb94d8 (diff) | |
| parent | a148746c073dd1c4b00d2387f2b77743d6c27004 (diff) | |
| download | nanowasm-design-ce509cdb9ec33fc439e389c82dffc1e641c1925d.tar.gz | |
Merge pull request #313 from dschuff/dl_separate_file
Factor dynamic linking section into its own file
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 |
