From 9c99bc0eb11651c6e557a40ef636391999c64203 Mon Sep 17 00:00:00 2001 From: nmlgc Date: Thu, 11 Nov 2021 14:23:01 +0100 Subject: [PATCH] [Contributing] Don't enforce preservation of symbol names from leaked ZUN code We can do much better ourselves. Part of P0168, funded by Blue Bolt and rosenrose. --- CONTRIBUTING.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 73a6e56b..a379d511 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -321,9 +321,12 @@ C++, Open Watcom, and Visual C++, which will ease future third-party ports. On some occasions, ZUN leaked pieces of the actual PC-98 Touhou source code during interviews. From these, we can derive ZUN's original names for certain -variables, functions, or macros. To indicate one of those and protect them -from being renamed, put a `/* ZUN symbol [reference] */` comment next to the -declaration of the identifier in question. +variables, functions, or macros. To indicate one of those, put a +`/* ZUN symbol [reference] */` comment next to the declaration and definition +of the identifier in question. Preserving any aspect from leaked ZUN code just +for the sake of it is not mandatory though, and in fact tends to make the +resulting code harder to understand. If you can come up with a better (or less +wrong) name, go for it. Currently, we know about the following [references]: