Re: [Oopic-compiler-devel] OOpic firmware versions and code generation impact

[Neil D. <nd...@us...>]

D. Daniel McGlothin wrote:
> However, since the firmware commands (the op-codes) also vary by version,
> won't the generator also need to be firmware aware?

I've just spotted something else in the op-codes.  Look at op-code 128,
"Aversion_Version".  The description says:

  "Compares the top stack item to the firmware version. Resets the OOPic if
  not equal or above."

This suggests the OOPic is backwards-compatible with code targeting older
OOPics, otherwise this instruction would be pointless.

So this indicates that our code generator can be firmware-independent for
all of the op-codes supported on the first firmware version, and then we
can have conditional logic to allow the use of newer op-codes when
targeting newer firmware versions wherever it is appropriate.

My gut feeling is that the newly-added op-codes are either to allow
optimisations to be made, or special instructions needed for the newer VC
objects.

Neil
-- 
Neil Durant
<nd...@us...>