diff options
| author | Luke Wagner <mail@lukewagner.name> | 2015-06-12 09:38:03 -0500 |
|---|---|---|
| committer | Luke Wagner <mail@lukewagner.name> | 2015-06-12 09:38:03 -0500 |
| commit | e8f1b6952ca1e3fda3fc3f2f9882b3da19b0bee8 (patch) | |
| tree | 18bcc58bcf0ba9e44b3b372584aaf62a78d3269b | |
| parent | b584d7177fddaae957eadf54b2ce0359d32022cc (diff) | |
| download | nanowasm-design-e8f1b6952ca1e3fda3fc3f2f9882b3da19b0bee8.tar.gz | |
Relink 'Web Platform' to Wikipedia; w3c/whatwg was too narrow anyhow
| -rw-r--r-- | Portability.md | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/Portability.md b/Portability.md index e1d2ee0..04fecb0 100644 --- a/Portability.md +++ b/Portability.md @@ -41,11 +41,12 @@ characteristics: WebAssembly does not specify any APIs or syscalls, only an [import mechanism](MVP.md#modules) where the set of available imports is defined by the host environment. In a [Web](Web.md) environment, functionality is -accessed through the Web APIs defined by the [Web](https://whatwg.org) -[Platform](http://w3c.org). Non-Web environments can choose to implement -standard Web APIs, standard non-Web APIs (e.g. POSIX), or invent their own. -Portability at the C/C++ level can, however, still be achieved by programming to -a standard API (e.g., POSIX) and relying on the compiler and/or libraries -to map the standard interface to the host environment's available imports either +accessed through the Web APIs defined by the +[Web Platform](https://en.wikipedia.org/wiki/Open_Web_Platform). Non-Web +environments can choose to implement standard Web APIs, standard non-Web APIs +(e.g. POSIX), or invent their own. Portability at the C/C++ level can, however, +still be achieved by programming to a standard API (e.g., POSIX) and relying +on the compiler and/or libraries to map the standard interface to the host +environment's available imports either at compile-time (via `#ifdef`) or run-time (via [feature detection](FeatureTest.md) and [dynamic loading](MVP.md#modules)). |