View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0031558 | 2.x IDE Bugs | Compiling | Public | 2019-12-31 15:55 | 2020-01-20 13:55 |
Reporter | Dan | Assigned To | Russell Kay | ||
Priority | Medium | Severity | C - General | Reproducibility | 100% |
Status | Resolved | Resolution | Fixed | ||
Platform | - | OS | Windows 10 | OS Version | Pro x64 |
Product Version | 2.2.5 | ||||
Target Version | 2.3.0 | Fixed in Version | 2.3.0 | ||
Summary | 0031558: Compiling: Using a whole array in a for() expression is not treated as a compiler error | ||||
Description | Using a whole array in a for() expression should be a compiler error saying you need to use an individual element of the array or the size of the array. Currently, different platforms will handle this coding mistake individually: Windows enters the loop, but bails when beyond the length of the array HTML5 seems to go into an infinite loop and locks up your browser tab Android does not go into the loop and so effectively silently ignores the coding error, but also means the game doesn't work as intended | ||||
Steps To Reproduce | 1. Run the attached sample for the platforms mentioned. 2. Observe at no time is this treated as a compiler error that you should fix your code Repro: 100% | ||||
Tags | No tags attached. | ||||
2.x IDE Found In | 2.2.5.481 | ||||
2.x Runtime Found In | 2.2.5.378 | ||||
2.x IDE Verified In | |||||
2.x Runtime Verified In | |||||
|
array_loop_bug.yyz (18,433 bytes) |
|
Is apparently fixed for 2.3.0 already, according to git commit messages. |