diff options
| author | Dan Gohman <sunfish@mozilla.com> | 2015-06-02 08:48:09 -0700 |
|---|---|---|
| committer | Dan Gohman <sunfish@mozilla.com> | 2015-06-02 08:48:09 -0700 |
| commit | aa59f86f3e2b49976fd429c8b74d9b97e62aa072 (patch) | |
| tree | 338178441ff44bf4ab5d700de21b2fd358d88f5e | |
| parent | d84e12434982efa2ac5b1d97efe038d305cf8dab (diff) | |
| download | nanowasm-design-aa59f86f3e2b49976fd429c8b74d9b97e62aa072.tar.gz | |
Fix spelling errors.
| -rw-r--r-- | V1.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -49,7 +49,7 @@ precise descriptions of: * When compiling from C++, imports would be generated for unresolved `extern` functions and calls to those `extern` functions would call the import. * Thus, in an environment with ES6 modules, to synchronously call into JS from - C++, the C++ code would declare and call an unndefined `extern` function and + C++, the C++ code would declare and call an undefined `extern` function and the target JS function would be given the (mangled) name of the `extern` and put inside the imported ES6 module. * TODO: there is more to discuss here concerning APIs. |