[
https://issues.apache.org/jira/browse/FLEX-33280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Crowl updated FLEX-33280:
-----------------------------
Description:
An ActionScript function executes unexpectedly when compiled using Ad-Hoc
release mode, using the Flex Packager for iOS.
The sample program contains a for each loop within another for each loop, that
is used to compare two lists of integers. At the start of the outer loop, a
variable named "matched" is set to false.
When a match is found in the inner loop, matched is assigned the value true,
and the inner loop issues a break command to early-exit the loop.
Following the inner loop, an if statement checks the value of the boolean
variable, like so:
if (matched == false)
{
...
}
When the code is execute as an adhoc iOS release build on an iPad 3, the code
within the if statement is executed even when matched == true.
Changing the code to the following, works as expected:
if (!matched)
{
...
}
was:
An ActionScript function works differently between debug and release builds
using the Flex Packager for iOS.
> [iOS] Packager compiles boolean condition incorrectly after loop break
> ----------------------------------------------------------------------
>
> Key: FLEX-33280
> URL: https://issues.apache.org/jira/browse/FLEX-33280
> Project: Apache Flex
> Issue Type: Bug
> Components: .Unspecified - Compiler, Installation & Packaging
> Affects Versions: Adobe Flex SDK 4.6 (Release)
> Environment: Windows 7 Ultimate
> Adobe Flex SDK 4.6 (build 23201, includes Adobe AIR 3.4 SDK)
> Flash Builder 4.5.1.313231
> Reporter: Ben Crowl
> Labels: ios, packaging
> Attachments: BasicMobile.zip
>
>
> An ActionScript function executes unexpectedly when compiled using Ad-Hoc
> release mode, using the Flex Packager for iOS.
> The sample program contains a for each loop within another for each loop,
> that is used to compare two lists of integers. At the start of the outer
> loop, a variable named "matched" is set to false.
> When a match is found in the inner loop, matched is assigned the value true,
> and the inner loop issues a break command to early-exit the loop.
> Following the inner loop, an if statement checks the value of the boolean
> variable, like so:
> if (matched == false)
> {
> ...
> }
> When the code is execute as an adhoc iOS release build on an iPad 3, the code
> within the if statement is executed even when matched == true.
> Changing the code to the following, works as expected:
> if (!matched)
> {
> ...
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
