Hi Alex, Thanks for looking into that. This is the hottest subject after the release and sadly to say arguable. Let's resolve it in this thread.
My results Chrome [1], Firefox [2] - Windows 7. 1) Strict equality - I'm for revert the to the previous version of code (hopefully Harbs will merge tlf branch soon) and teach compiler if we would like to achieve something else in that case if it's possible. I have never used strict equality and I will not till some client say to me - Hey our app is slowing down. For me differences are really small and not in all places we are gaining some performance boost. We cannot make happy everyone and we shouldn't. 2) Initializing by some default values: Cool!, by only with some compiler options without changing current code. [1] https://paste.apache.org/fA88 [2] <http://apache-flex-development.2333347.n4.nabble.com/file/n62681/firefox_.png> Thanks, Piotr ----- Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FLEXJS-FALCONJX-Variable-Initialization-equality-etc-tp62675p62681.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
