Rooba
/
ReC98
mirror of https://github.com/nmlgc/ReC98.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[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.
This commit is contained in:
nmlgc 2021-11-11 14:23:01 +01:00
parent 488115513c
commit 9c99bc0eb1
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
CONTRIBUTING.md
View File

@ -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 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 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 variables, functions, or macros. To indicate one of those, put a
from being renamed, put a `/* ZUN symbol [reference] */` comment next to the `/* ZUN symbol [reference] */` comment next to the declaration and definition
declaration of the identifier in question. 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]: Currently, we know about the following [references]: