From 056a317e542ffb36e1fb4028d382c9e56251c9ba Mon Sep 17 00:00:00 2001
From: David Brown <dave.github@brownsmeet.com>
Date: Thu, 24 Nov 2016 18:10:51 +0000
Subject: [PATCH] Remove SetHalt documentation - code was already disabled.

---
 doc/Features.md         | 2 --
 src/runtime/Modules.Mod | 5 -----
 2 files changed, 7 deletions(-)

diff --git a/doc/Features.md b/doc/Features.md
index e597732c..ae0bcc43 100644
--- a/doc/Features.md
+++ b/doc/Features.md
@@ -144,5 +144,3 @@ HALT displays the message 'Terminated by Halt(n)'. For negative values that corr
 
 Bear in mind that both Linux and Windows generally treat the return code as a signed 8 bit value, ignoring higher order bits. Therefore it is best to restrict HALT and ASSERT codes to the range -128 .. 127.
 
-A client application may register a halt handler by calling Platform.SetHalt(p) where p: PROCEDURE(n: SYSTEM.INT32). This procedure will be called before Halt displays it's message. The procedure may suppress the Halt message by calling Platform.Exit(code: INTEGER) directly.
-
diff --git a/src/runtime/Modules.Mod b/src/runtime/Modules.Mod
index d6b8eeeb..12fbcd7a 100644
--- a/src/runtime/Modules.Mod
+++ b/src/runtime/Modules.Mod
@@ -151,9 +151,4 @@ MODULE Modules;  (* jt 6.1.96 *)
     Platform.Exit(code);
   END AssertFail;
 
-  (*
-  PROCEDURE SetHalt*(p: HaltProcedure);
-  BEGIN HaltHandler := p; END SetHalt;
-  *)
-
 END Modules.