If you have some code that allows string comparison in compile-time conditionals, then I think adding a string valued "$flexversion" would work. The legal values that exist for now would be "10.0" and "10.1".
On Sat, Dec 11, 2010 at 11:16 AM, André Bargull <[email protected]>wrote: > Do you think a string-constant is sufficient, e.g. $flexversion? > I've got an extended compile-time evaluator which also supports string > comparison, so there is no issue wrt the current evaluator - like the > ClassCastException in LPP-9582. > > > > > On 12/11/2010 4:10 PM, Henry Minsky wrote: > >> We don't have a compile time constant right now, but I could add one. >> >> There's an option that can be supplied now via the lzc command line or >> the new URL options(...) list, >> >> "--flex-options=version=10.x,air,debug", >> >> Internally that string is stored in the compiler options hashtable as >> >> Compiler.FLEX_OPTIONS = "flexoptions" >> >> And in sc/SWF9External there's some code that parses out the version in >> order to pass the flag >> to the flex compiler. That's the only place it's used now. >> >> I can add a javascript compile time constant for it. Can you file a JIRA >> task and assign to me? >> >> >> On Sat, Dec 11, 2010 at 9:34 AM, André Bargull <[email protected] >> <mailto:[email protected]>> wrote: >> >> Is there any way to check the "flexversion" property at runtime >> resp. at compile-time? So something similar to the compile-time >> constants like "$swf10", "$swf9" etc. This is important when you >> want to import class definitions for swf10.1, for example. >> >> >> >> >> -- >> Henry Minsky >> Software Architect >> [email protected] <mailto:[email protected]> >> >> >> -- Henry Minsky Software Architect [email protected]
