-
23 Nov 2012 5:54 AM #1
Ext.Array.intersect bug
Ext.Array.intersect bug
Hello Sencha,
I've found a bug in the Ext.Array class in the intersect method. I presume it's there in all versions.
In the main loop for traversing the minimum array, the for loop has the conditions
In the condition that's evaluated after each iteration, someone has been a little too clever and written the conditionCode:for (i = 0,ln = minArray.length; i < ln,x = minArray[i]; i++)
This comma expressions ignores the actual result of the loop and returns the second expression as the result.Code:i < ln,x = minArray[i]
In my case, there is a 0 in the array of values, causing the look to stop prematurely.
-
23 Nov 2012 7:08 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,581
- Vote Rating
- 433
Thanks for the report! I have opened a bug in our bug tracker.
-
26 Nov 2012 1:40 PM #3
one kind of bad programmers practice :P
Success! Looks like we've fixed this one. According to our records the fix was applied for
TOUCH-3748
in
Sprint 29.


Reply With Quote