split g into multiple structures
The consolidation of global variables from scattered source
files into decl.c and declared in decl.h was begun in 3.7.0.
Their placement in common files was done for centralized
initialization and potential re-initialization during a
"play again" scenario.
It wasn't really necessary for all of them to be housed in a
single huge structure to meet the "play again" requirement,
and the single huge structure has been a little unwieldy when
it comes to maintenance.
Following this commit, instead of one single extremely large structure
named 'g' to house all of the relocated global variables, they
are distributed into several ga through gz.
To make things easy for the developer, each variable is placed
into the struct corresponding to the starting letter of the variable.
That way, no lookup is required in order to know which struct houses
a particular variable, it is a simple match to the starting letter
for all the centralized global variables.
A global variable named 'amulets', would be found in ga.
ga.amulets
^ ^
A global varable named 'move', would be found in gm.
gm.moves
^ ^
A global variable named 'val_for_n_or_more' would be found in gv.
gv.val_for_n_or_more
^ ^
A global variable named 'youmonst' would be found in gy.
gy.youmonst
^ ^
This commit is contained in:
7
README
7
README
@@ -46,9 +46,10 @@ process. Among them:
|
||||
|
||||
* Add support to make the game restartable without exit (a.k.a. "play again"
|
||||
support). Toward that end, many previously scattered and separate variables
|
||||
have been gathered into a central 'g' structure in decl.h/decl.c. That
|
||||
will benefit the porting effort to some platforms that are under
|
||||
consideration.
|
||||
have been gathered into central 'ga' through 'gv' structures in
|
||||
decl.h/decl.c. That central ability to reinitialize the variables will
|
||||
benefit the porting effort to some platforms that are under consideration
|
||||
where "play again" is typical.
|
||||
|
||||
Here are some other general notes on the changes in NetHack 3.7 that were not
|
||||
considered spoilers:
|
||||
|
||||
Reference in New Issue
Block a user