On 3/14/17, 11:17 PM, "Greg Dove" <greg.d...@gmail.com> wrote:
>to clarify : > >I got the typedefs building eventually and compiling the single arg >signature for partseInt is fine, but the compiler makes a fixed assumption >for 10 radix for any string and adds that second param instead of allowing >the native implementation to do its thing. OK, good to know your typedefs are good. I agree that 10 is wrong, but reading both AS and JS doc, I'm now thinking that if the second argument is missing that the compiler should use 0. > >If there are string formats like octal that get inferred differently from >the string in js but not in swf then that complicates things but if they >are identical (and if there is no requirement to have the js output *not* >have an optional argument) then the simplest thing of course is to pass it >through unchanged. > >I will check the various browsers and permutations this weekend to see >what >happens. I already added a ticket for me Thanks for digging into it. -Alex
