Community
Participate
Working Groups
Created attachment 209654 [details] Compare using beyondCompare Compare to the result of 0.7, the some of the variation in the test cases failed when they are passed in 0.7 api.eglx_lang.EAny001 fvt.datatypes.TestAnyTypeLib fvt.datatypes.TestCollectionsLib fvt.json.JSONTestsLib fvt.operators.TestIsaOperatorLib fvt.primitives.TestDictionaryLib fvt.xml.CDATALib fvt.xml.FlexRecordLib fvt.xml.NullHandlingLib fvt.xml.weatherLi lang.expression.parameter.AnyParameters007 Please refer to the attached file for the comparison of the result of 0.7 and 0.8
I'll take a look at the differences, however, there was a change made to the eglar's that affect certain nullable conditions (PLUS change, etc), which might make the results that we were getting in 0.7 invalid, and might be correct now. That would mean the testcase needs fixing. We'll see when I get a look at it.
There was a change in the IR that caused about 90 of these failures. I have since added the 1 line of code that is needed in the EAny class that additionally checks for a comparison of 2 Number types. Previously, this was not needed, as this comparison was sent to the ENumber class for comparison. Which this IR change, only some got sent over. There are a few differences now left and I am investigating.
I found a bug in the function invocation logic where it was trying to determine if boxing expressions needed to be altered to wraps. The logic was not handling embedded expressions. This change has been released to cvs. It fixes several more of the problems. There are now only 9 differences left. Will continue working on it.
There is 1 outstanding issue having to do with Isa on an anyboxedobject of an array. I am opening a new defect for this, and marking this as resolved.
Verified in build 0.8.0.v201202190901-1Co-FjuJ6QMNRcrynsZh8h8C
