Before, when I tried to patch the framework code, I'd routinely delete
`include "core/Version.as"' lines, it didn't seem to have any impact on the
existing code. This can be imprecise, because I'd usually try to reduce the
number of classes to compile, but it looks more like it wasn't used often
enough to justify the mandatory use.
There are other ways to identify the version -
* @langversion 3.0
* @playerversion Flash 9
* @playerversion AIR 1.1
* @productversion Flex 3
I don't see why this is not enough. If someone wants to be more pedantic,
then they can elaborate on @productversion. I'm not in favor of adding
compiler stamps, or extra metadata because the chances are it will quite
often became an obstacle rather then helper, just like a bunch of pointless
compiler warnings that MXMLC has, which actually resulted in that
programmers developed practices of writing bad code to only make the
compiler shut up ("missing parenthesis after function" warning is one such
example).
