diff options
| author | JF Bastien <github@jfbastien.com> | 2015-06-01 12:54:56 -0700 |
|---|---|---|
| committer | JF Bastien <github@jfbastien.com> | 2015-06-01 12:54:56 -0700 |
| commit | d84e12434982efa2ac5b1d97efe038d305cf8dab (patch) | |
| tree | a7a40a85b28a2c519cbeb966e14b411cd99eb3ae | |
| parent | e14b446e0be23cdd7e264659777db9693d6c3b2c (diff) | |
| parent | cd8aae95e274a823602c10e3bcba18ef7b58db0a (diff) | |
| download | nanowasm-design-d84e12434982efa2ac5b1d97efe038d305cf8dab.tar.gz | |
Merge pull request #92 from WebAssembly/incompletely-specified-behavior.md
Clarify the incompletely specified behavior wording
| -rw-r--r-- | IncompletelySpecifiedBehavior.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/IncompletelySpecifiedBehavior.md b/IncompletelySpecifiedBehavior.md index f577772..8f825a7 100644 --- a/IncompletelySpecifiedBehavior.md +++ b/IncompletelySpecifiedBehavior.md @@ -1,10 +1,10 @@ # Incompletely Specified Behavior -WebAssembly is a sandboxed platform. Programs can't access data outside the sandbox without going through appropriate APIs, or otherwise escape the sandbox, even if the behavior inside the sandbox should ever be unspecified in any way. +WebAssembly is a sandboxed platform. Applications can't access data outside the sandbox without going through appropriate APIs, or otherwise escape the sandbox, even if the behavior inside the sandbox should ever be unspecified in any way. -Beyond that, it is desirable to minimize observable differences between implementations when practical, so that programs don't inadvertently become dependent on any particular implementation's behavior. However, in some areas, performance concerns make this prohibitively expensive, so some compromises are made. +Beyond that, it is desirable to minimize observable differences between implementations when practical, so that applications don't inadvertently become dependent on any particular implementation's behavior. However, in some areas, performance concerns make this prohibitively expensive, so some compromises are made. -Also, there is a general preference against [nasal demons](https://en.wikipedia.org/w/index.php?title=Nasal_demons). WebAssembly generally prefers to [trap](AstSemantics.md) in many situations. Otherwise, it is generally preferred to have a specific set of possible behaviors rather than unconstrained behavior. And presently, WebAssembly has no nasal demons. +Also, there is a general preference against [nasal demons](https://en.wikipedia.org/w/index.php?title=Nasal_demons), since they are an extreme on the spectrum of observable differences, and since they make it difficult to reason about what state an application might be in. WebAssembly usually prefers to [trap](AstSemantics.md). Otherwise, it is generally preferred to have a specific set of possible behaviors rather than nasal demons. And presently, WebAssembly has no nasal demons. The following is a list of the places where the WebAssembly specification currently admits or is expected to admit multiple possible behaviors. |