aboutsummaryrefslogtreecommitdiff
path: root/Modules.md
diff options
context:
space:
mode:
authorDerek Schuff <dschuff@chromium.org>2015-08-26 14:42:18 -0700
committerDerek Schuff <dschuff@chromium.org>2015-08-26 14:42:18 -0700
commitce509cdb9ec33fc439e389c82dffc1e641c1925d (patch)
tree7f7884596f2e5ea90297ad7279ab86272025a113 /Modules.md
parent773dca0adefcdd44e6cbced6507822c1bfdb94d8 (diff)
parenta148746c073dd1c4b00d2387f2b77743d6c27004 (diff)
downloadnanowasm-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.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Modules.md b/Modules.md
index e07e4b6..1210faf 100644
--- a/Modules.md
+++ b/Modules.md
@@ -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