After adding an AfterAction (notice the initial uppercase A !!) to a thing (inside the thing’s definition, note also this detail), the compiler behaves strangely, recompiling every .o file and generating a 40+K bigger binary.
of course, I noted the camelCase issue, and after giving the correct casing (afterAction), the binary was of the expected ~512 bytes bigger, but on manual-based theory, the added method (the apparently predictable outcome of the typo, should be local to the thing, but in this specific case, the method was unexpected (and arbitrary ?) added to many other items/classes &c. (the specific thing is a Fixture, that is, a shallow equivalent of an adv3 class)
well, of course I was spared a bug-hunting for a property turned into an unreachable code, but that ends recompiling all .o, generating a sizeably bigger binary is rather puzzling.
Someone has an explanation for this compiler’s (mis?)behaviour ?
Perplexed regards from Italy,
dott. Piergiorgio.