From d59fd50600832273444db10c3314858393bc2e54 Mon Sep 17 00:00:00 2001
From: Deven Blake <trinity@trinity.moe>
Date: Tue, 31 May 2022 01:05:46 -0400
Subject: [PATCH] tear down embarrassingly flawed article until i get it right

---
 homepage/knowledge/c78.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/homepage/knowledge/c78.html b/homepage/knowledge/c78.html
index 1705621..2a704fd 100644
--- a/homepage/knowledge/c78.html
+++ b/homepage/knowledge/c78.html
@@ -48,7 +48,7 @@ This page documents those incompatibilities and relative oddities.
 I have never done (and probably never will do) extensive programming in pre-ANSI C.
 These incompatibilities were discovered out of Appendix C in <I>The C Programming Language, 2nd ed.</I> but are described further.
 </P>
-<H2 ID="octal89"><CODE>8</CODE> and <CODE>9</CODE> as valid octal digits</H2>
+<!--<H2 ID="octal89"><CODE>8</CODE> and <CODE>9</CODE> as valid octal digits</H2>
 <PRE>
 main()
 {
@@ -80,5 +80,6 @@ This file provides <CODE>getnum</CODE>, a function used in <CODE>/usr/source/c/c
 My theory is that this behavior is a side-effect of a very efficient but imperfect method of parsing integer constants from a file stream,
 and that this implementation was "good enough" and informally the behavior of a C compiler supplied invalid octal constants was just undefined.
 </P>
+-->
 </BODY>
 </HTML>