I have moved this example to be the first of the test cases. If `MATCH(2,1)` isn't `#N/A` because of the unsorted array, then surely it should be `1` (item 1 of the array is the largest number less than or equal to the lookup value) but Excel and PhpSpreadsheet (before and after changes) return `2`. However, when match_type is not zero, the match array is supposed to be sorted, so I would expect `#N/A` when it isn't but that's not how Excel operates.
PhpSpreadsheet's results match Excel's, so no problem. I note that Excel doesn't seem to follow its own rules for MATCH ( ). Just using the already available wildcard functions whenever comparing two strings is sufficient. Although it would have been easy to just add that, I think it was wrong to determine on its own if a wildcard was in use. It ignored tilde as a wildcard character. In addition, the wildcard logic in matchFirstValue is faulty. However, matchLargestValue seemed to handle things correctly - but see below. Adding test cases, it seems that matchFirstValue had the same problem. Function matchSmallestValue did not recognize that an integer could match a float. MATCH Problems with Int/Float Compare and Wildcards ( #3142 ) * MATCH Problems with Int/Float Compare and Wildcardsįix #3141.
0 kommentar(er)
