If the compiler outputs 10 for everything then it is different to actionscript which checks for "0x" and decides on 16 or 10 We can change the behaviour, but it won't be identical to : "Strings beginning with 0x are interpreted as hexadecimal numbers"
Maybe it is better to not support '0x' strings and make developers check and specify the 16 radix on the substrings....but it is not consistent with orignal version On Wed, Mar 15, 2017 at 6:07 PM, Alex Harui <aha...@adobe.com> wrote: > > > On 3/14/17, 9:54 PM, "Greg Dove" <greg.d...@gmail.com> wrote: > > >Alex, I agree, it seems whatever prompted this was elsewhere, but the > >outcome is IMO (a small amount of) better framework code in CSSUtils. > >I would take this as a small win - nothing is broken, and a utility method > >is theoretically slightly faster. > > I am still confused. If the compiler should output JS that specifies 10 > for the second parameter if not specified because that will net > better/faster code we should definitely do that. But I don't understand > any reason to actually add the second parameter in the ActionScript source. > > Thanks, > -Alex > >
