You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
menu_setting: two builders become data, their bodies deleted
The generic desc-group walker already runs the cheats, crt and
turbo-fire lists from registry data with no code. Two more join
them: frame_time_counter, whose two adjacent row files concatenate
into one table now that the auto-reset hide moved to the
displaylist, and steam, always a single table. Both build
functions delete; their registry entries carry the rows, counts
and group enums the walker needs. Net 43 lines out, and two fewer
functions in .text.
That is the whole safe yield this round, and the reason is worth
recording. Of the forty-odd remaining builders, one runs a
runtime capability check per row (gamemode), one customizes after
construction (the LV widget-scale residue), one splits its two
tables under different compile guards (accounts), and thirty-eight
construct settings by hand with CONFIG_* rather than descriptor
tables. The walker cannot swallow any of those without either
runtime-condition and compile-guard columns in the registry - real
grammar, not a macro - or migrating the hand CONFIG_* settings into
def files first. The hand-CONFIG migration is the large lever and
the honest next objective; the walker was never going to clear
more than a handful until it lands.
0 commit comments