From a7ddd6337517864d8ae44a20b8225046b6d6fdf3 Mon Sep 17 00:00:00 2001
From: Simon Tatham <anakin@pobox.com>
Date: Sun, 20 Apr 2014 08:47:27 +0000
Subject: [PATCH] Change our method of calling main() in emccpre.js.

I've just upgraded to emcc 1.16.0, in which something fiddly has
happened to the semantics of Module.run() vs noInitialRun - now
setting the latter seems to cause the former to do everything except
calling main(), and then refuse to ever do anything again. So now I
have to use Module.callMain() in place of Module.run() when I finally
do get round to wanting to call main().

[originally from svn r10180]
---
 emccpre.js | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/emccpre.js b/emccpre.js
index 5231d04..fef83c1 100644
--- a/emccpre.js
+++ b/emccpre.js
@@ -352,8 +352,7 @@ function initPuzzle() {
     // Run the C setup function, passing argv[1] as the fragment
     // identifier (so that permalinks of the form puzzle.html#game-id
     // can launch the specified id).
-    Module.arguments = [location.hash];
-    Module.run();
+    Module.callMain([location.hash]);
 
     // And if we get here with everything having gone smoothly, i.e.
     // we haven't crashed for one reason or another during setup, then