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

[D. D. M. <Da...@Mc...>]

Something I received from Scott Savage, but had not passed on yet.

I asked:

>With regard to the 'OOPicObjectCommandList', am I correct in understanding
>that
>each newer firmware version only added objects or commands?
>
>In other words, to support multiple firmware versions, is it only a matter
>of
>filtering the commands/objects by the version they first appeared in?  If
>so,
>and for the case of the object commands, would you have available a
>cross-reference as to which firmware version the  object command became
>available.

and Scott replied on 07-MAY-2004:

<quote>
Yes new commands and object were added with each version.

However, the sales of the versions below II+ are only about 10% of total
sales.

Given that, I think it would be best to work with just the II+ version.

Give me a few more days on the Object database.
</quote>


Several points:

1. Although have not yet received the 'Object database', we do have some
information about the firmware differences.

2. Since firmware version II+ is 90% new sales, that is the reasonable first
target for the toolchain.  However, the statitistic does not comment to the
relative sizes of the shipped populations.

3. How would the project accomodate different versions of the firmware?  Is
it a matter of a different code generator for each firmware, or does one
generator handle the differences conditionally?

Daniel