So he needs to patchup
* all pointers in all new objects,
* all pointers into the old-range,
* and all live on-stack values into their new on-stack locations.
Did I forget something? using volatile-only vars would solve only the third problem.
* all pointers in all new objects,
* all pointers into the old-range,
* and all live on-stack values into their new on-stack locations.
Did I forget something? using volatile-only vars would solve only the third problem.
It's not to say that this would be a reasonable thing to do, but that these sort of shenanigans may be done (e.g. to pass data across an excessively narrow API callback)
* all arrays of such structs.
Dealing with deleted fields is more or less straightforward, but what should be put into newly added fields is anyone's guess.
Edit: Or just live with the fact that certain kinds of changes require a program restart.