flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Dove (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-35283) parseInt Implementation
Date Tue, 21 Mar 2017 18:07:41 GMT

    [ https://issues.apache.org/jira/browse/FLEX-35283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934999#comment-15934999

Greg Dove commented on FLEX-35283:

I assume GCC made the 2nd parameter 'required' to avoid slower performance in situations where
the radix ought to be known, or could easily be known by the developer. So it's almost like
a 'behavioural optimization' of the js developer, because they must make a conscious decision
In our case we continue to let actionscript developers take the easy route, which might mean
code that runs slower in cases where the developer could easily add the radix when they did
not (because they know what it should be) and have it run faster. 

> 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

View raw message