flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From OmPrakash Muppirala <bigosma...@gmail.com>
Subject Re: [2/2] git commit: [flex-falcon] [refs/heads/develop] - apparently, parseInt in JS should always specify the radix
Date Thu, 17 Mar 2016 02:09:48 GMT
On Wed, Mar 16, 2016 at 7:03 PM, Andy Dufilie <andy.dufilie@gmail.com>
wrote:

> The latest browsers do not support the octal case anymore so I'm inclined
> to say it should be left alone.  I doubt it would ever be an issue.
>

In that case, Alex's option 2 will ensure that it will work the same way
across Flash, older browsers and newer browsers.

Thanks,
Om


>
> On Tue, Mar 15, 2016 at 7:55 PM, Alex Harui <aharui@adobe.com> wrote:
>
> >
> >
> > On 3/15/16, 3:57 PM, "omuppi1@gmail.com on behalf of OmPrakash
> Muppirala"
> > <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
> >
> > >I think the problematic part is where strings start with "0".  There
> might
> > >be some browsers adding a radix of 8.  This is a supposedly deprecated
> > >feature.  There is no way of knowing what the browser would do by
> default
> > >in this case.
> >
> > OK, so this is all about radix=8?
> >
> > I guess that leaves us two choices:
> > 1) Do what Andy says and just make the second param optional and see if
> > anyone gets burned if they are assuming a leading 0 will not be
> translated
> > as radix=8 because that's how I understand Flash/AIR works
> > 2) Map parseInt to Language.parseInt and have Language.parseInt check for
> > leading 0 not followed by "x" and set radix = 10 to guarantee exact match
> > with Flash/AIR?
> >
> > Either one is fine with me.
> >
> > Thoughts?
> > -Alex
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message