[
https://issues.apache.org/jira/browse/FLEX-35283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932807#comment-15932807
]
Alex Harui commented on FLEX-35283:
-----------------------------------
I think we should use 0. AFAICT, 0 and undefined are result in the same thing,
but AS defines the second parameter as a uint. Actually, it seems like a bug
that the SWF compiler allowed undefined.
> parseInt Implementation
> -----------------------
>
> Key: FLEX-35283
> URL: https://issues.apache.org/jira/browse/FLEX-35283
> Project: Apache Flex
> Issue Type: Bug
> Components: FalconJX
> Affects Versions: Apache FalconJX 0.8.0
> Reporter: Greg Dove
> Assignee: Greg Dove
>
> parseInt does not correctly process hex strings without no second parameter
> parseInt("0x99")
> this should calculate as 153
> it is currently compiled to
> parseInt("0x99",10)
> in js which evaluates to 0
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
