The pin advanced with the recale, so twenty-five romset refs stopped
naming the line that declares their set at the new revision.
mame_ref_audit found and moved them; 147 agree, 180 refs anchored.
dinothawr's libretro.cpp became libretro.c and its refs already carried
the new line numbers, so the pin followed. groovymame cited a Batocera
package recipe and jgenesis a RetroBat generator, neither of which lives
in the tree each names; both read external now.
profile_sync follows content, so a ref that drifted still anchors where
the cited text went. That is drift detection working, and it cannot
answer the only question a MAME romset ref asks: does this line declare
this set. It flagged five refs in one driver file where nineteen were
stale, the fourteen others having been relocatable somewhere plausible.
mame_ref_audit asks the stronger question and found ninety-two across
the four profiles whose upstream still moves: mame 66, mamearcade 18,
mamemess 6, groovymame 2. Each had exactly one declaration to point at.
The frozen generations, mame2009 through mame2016, come out clean, which
is the check saying it finds drift only where drift can happen.
The set name is argument 1 of the machine macro. Matching it anywhere on
the line matches every clone naming it as parent, which is most of a
driver, and comments are stripped first because a declaration can sit
behind one. A set no machine declares is reported as not judgeable, not
wrong: device archives take their DEFINE_DEVICE_TYPE shortname.
Abdessamad Derraz