the reference tables, the install guard and the vendored forks stop naming the maintainer's analysis

The notes and comments say what is true of the 1.12.1 client and cite the
byte address; the record numbers, the dates and the private repository's
file paths go.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Sam
2026-09-23 18:47:48 +07:00
co-authored by Claude Fable 5.1
parent 7e4cf3a054
commit 23c14aaec1
8 changed files with 192 additions and 279 deletions
+3 -4
View File
@@ -201,7 +201,7 @@
** CHANGE it if you want a different appearance.
*/
/*
** BENILLA (decision 2122): 1.12's Lua is 5.0, which quotes every program element in an error
** BENILLA: 1.12's Lua is 5.0, which quotes every program element in an error
** message with a BACKQUOTE and an apostrophe. 5.1 introduced this macro and made it two
** apostrophes. Read out of WoW.exe's own .rdata, which carries all five of the formats this macro
** feeds, in the 5.0 spelling:
@@ -368,9 +368,8 @@
** off the advisory error when nesting [[...]].
*/
/* BENILLA: 2, the 5.0 behaviour. 1.12.1 ships Lua 5.0, where `[[ ... [[ ... ]] ... ]]`
** nests; 5.1 kept the machinery and put an advisory error in front of it. Two corpus
** addons stop loading on "nesting of [[...]] is deprecated" — a 5.1 opinion about a
** dialect we are not targeting. Same family as the OP_TFORPREP restoration (1215).
** nests; 5.1 kept the machinery and put an advisory error in front of it, on which two
** corpus addons stop loading ("nesting of [[...]] is deprecated").
*/
#define LUA_COMPAT_LSTR 2