8 Feb
2012
8 Feb
'12
4:02 p.m.
Chuck Guzis wrote:
Contrast this with P-code implementations, or CPU
emulatons, where the
program never gets control of the real P-counter--it's always being
managed by the P-code interpreter or the emulation package. --Chuck
But P-code isn't considered to be native code either.
If you go down the path of calling Sweet16 code and P-code "native
code", then the phrase "native code" no longer has any meaning. At that
point you can claim that any program ever written for a stored-program
digital computer is "native code" for my PDP-8, because if I add enough
storage to the PDP-8 and spend enough time writing a simulator, I can
run it.