More notes for xVS_cal_wasm.js
This commit is contained in:
parent
8b612c765a
commit
d0b95065a9
|
|
@ -1,19 +1,8 @@
|
||||||
|
// xVS_cal_wasm.js - xVS wasm version calculation kernel, IT IS NOT A MOD.
|
||||||
|
|
||||||
// include: shell.js
|
// include: shell.js
|
||||||
// include: minimum_runtime_check.js
|
// include: minimum_runtime_check.js
|
||||||
// end include: minimum_runtime_check.js
|
// end include: minimum_runtime_check.js
|
||||||
// The Module object: Our interface to the outside world. We import
|
|
||||||
// and export values on it. There are various ways Module can be used:
|
|
||||||
// 1. Not defined. We create it here
|
|
||||||
// 2. A function parameter, function(moduleArg) => Promise<Module>
|
|
||||||
// 3. pre-run appended it, var Module = {}; ..generated code..
|
|
||||||
// 4. External script tag defines var Module.
|
|
||||||
// We need to check if Module already exists (e.g. case 3 above).
|
|
||||||
// Substitution will be replaced with actual code on later stage of the build,
|
|
||||||
// this way Closure Compiler will not mangle it (e.g. case 4. above).
|
|
||||||
// Note that if you want to run closure, and also to use Module
|
|
||||||
// after the generated code, you will need to define var Module = {};
|
|
||||||
// before the code. Then that object will be used in the code, and you
|
|
||||||
// can continue to use Module afterwards as well.
|
|
||||||
var Module = typeof Module != 'undefined' ? Module : {};
|
var Module = typeof Module != 'undefined' ? Module : {};
|
||||||
|
|
||||||
// Determine the runtime environment we are in. You can customize this by
|
// Determine the runtime environment we are in. You can customize this by
|
||||||
|
|
@ -901,3 +890,4 @@ run();
|
||||||
|
|
||||||
// end include: postamble.js
|
// end include: postamble.js
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue