summary
If you have VS2013, can you tell me the result of FileStorage_DMatch from opencv_test_core ?
Description
I'm using the master branch and realized that following three tests were failing
FileStorage_DMatchFileStorage_DMatch_vectorFileStorage_DMatch_vector_vector
All of them comes from opencv_test_core
I'm using VS2012 on 64bit Win7.
I digged in a while, and I came to a conclusion that this test failure is fixed behavior for VS2012.
For example, in test FileStorage_DMatch, the expected result is hard coded as
"%YAML:1.0\n---\nd: [ 1, 2, 3, -1.5000000000000000e+00 ]\n"
when the actual result is
"%YAML:1.0\n---\nd: [ 1, 2, 3, -1.5000000000000000e+000 ]\n"
Please note that the number of the last 0s are the only difference.
I traced a bit and I this comes from the result of sprintfof VS2012, and there is no other option to modify the result.
Question
I don't have other compiler than VS2012, but having a look to pullrequest.opencv.org, I believe this behavior is normal for VS2015 and modern GCC. I'm planning to create PR to fix this result, but before that, I'm not sure about the behavior of VS2013.
I guess the behavior of VS2010 and older will be same as VS2012. Also, the behavior of VS2017 and later will be same as VS2015. I have no idea what will happen for VS2013.
If anyone can try this situation on VS2013 (i.e. whether these tests from master will fail or not) I'm happy to hear the result.