Fixes in html files of 1990
This commit is contained in:
1 parent
c86d5ecd56
commit
ec7c48cd59
14 files changed
+60
-36
No files matched your search
+1
-1
@@ -45,7 +45,7 @@ than 4, but when I do that I get a complaint "defines nested too deeply".
|
||||
|
||||
### Obfuscation spoiler:
|
||||
|
||||
This is another rot13 job (believe it or not) - the `#defines` are a
|
||||
This is another rot13 job (believe it or not) - the `#define`s are a
|
||||
novel way of adding tokens: `#define b12(x) 12 x` means that at
|
||||
some point in the source a `12` is followed by the compressed nested
|
||||
`#define`s. The `b12` gets the previous compression as an argument, and
|
||||
|
||||
+1
-1
@@ -419,7 +419,7 @@ which we have done for the wider audience.</p>
|
||||
<p>If my preprocessor could hack it, I could write this as one single line rather
|
||||
than 4, but when I do that I get a complaint “defines nested too deeply”.</p>
|
||||
<h3 id="obfuscation-spoiler">Obfuscation spoiler:</h3>
|
||||
<p>This is another rot13 job (believe it or not) - the <code>#defines</code> are a
|
||||
<p>This is another rot13 job (believe it or not) - the <code>#define</code>s are a
|
||||
novel way of adding tokens: <code>#define b12(x) 12 x</code> means that at
|
||||
some point in the source a <code>12</code> is followed by the compressed nested
|
||||
<code>#define</code>s. The <code>b12</code> gets the previous compression as an argument, and
|
||||
|
||||
Reference in new issue
Block a user