diff options
| author | JF Bastien <jfb@chromium.org> | 2015-06-08 20:04:59 +0200 |
|---|---|---|
| committer | JF Bastien <jfb@chromium.org> | 2015-06-08 20:04:59 +0200 |
| commit | ca62f96dcbf265a2cda6a0b794e2107e7f86f097 (patch) | |
| tree | 15af70df757580a8fee9df8723a128d712d7e9eb | |
| parent | 39aaca82754ba55759790f333ad57036bc2ca620 (diff) | |
| download | nanowasm-design-ca62f96dcbf265a2cda6a0b794e2107e7f86f097.tar.gz | |
Clarify _start/init examples.
| -rw-r--r-- | MVP.md | 6 |
1 files changed, 2 insertions, 4 deletions
@@ -20,10 +20,8 @@ separate docs with more precise descriptions of: * The primary unit of loadable, executable code is a **module**. * A module can declare a subset of its functions and global variables to be **exports**. The meaning of exports (how and when they are called) is defined - by the host environment. - * `_start` can be the only meaningful export. - * An `init` method could always be called after loading a module and before - any other exports are called. + by the host environment. For example, `_start` and `init` can be the only + meaningful exports. * A module can declare a set of **imports**. An import is a tuple containing a module name, export name, and the type to use for the import within the module. The host environment controls the mapping from module name to which |
