> ... So I would expect to find serious bugs when doing this. That's actually a good point hmmm (not in case of this specific assembler, which seems to be quit

> ... So I would expect to find serious bugs when doing this. That's actually a good point hmmm (not in case of this specific assembler, which seems to be quite robust and well-written), and even if there would be serious memory corruption errors lurking, they would be contained because the assemblers runs in a WASM VM. For projects that are still maintained, a "moving standard" isn't that much of a problem, after all we've been conditioned that every new compiler update adds new warnings which "break" existing code ;) ...there is a certain value in taking a "finished/frozen" project and integrate that into a new project without requiring code changes though. I'm sure there must be a good middle-ground for C, where obviously bad and outdated language features (starting with leftovers from the K&R era) can be removed without causing too much breakage even on most old code ... but then, why keep 'inline' ;P