I compiled the 1.0.6 release for Windows ia32 systems and I observed compilation warnings.
These warnings didn't exist last week in the master branch. I don't see any problem at runtime so far.
Building Custom Rule C:/node-rfc/CMakeLists.txt
node_sapnwrfc.cc
Client.cc
C:\node-rfc\src\Client.cc(702,56): warning C4244: 'argument': conversion from 'uint64_t' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
rfcio.cc
noderfcsdk.cc
Throughput.cc
C:\node-rfc\src\Throughput.cc(110,56): warning C4244: 'argument': conversion from 'uint64_t' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
C:\node-rfc\src\Throughput.cc(132,5): warning C4244: 'argument': conversion from 'SAP_ULLONG' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
C:\node-rfc\src\Throughput.cc(133,5): warning C4244: 'argument': conversion from 'SAP_ULLONG' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
C:\node-rfc\src\Throughput.cc(134,5): warning C4244: 'argument': conversion from 'SAP_ULLONG' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
C:\node-rfc\src\Throughput.cc(135,5): warning C4244: 'argument': conversion from 'SAP_ULLONG' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
C:\node-rfc\src\Throughput.cc(136,5): warning C4244: 'argument': conversion from 'SAP_ULLONG' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
C:\node-rfc\src\Throughput.cc(137,5): warning C4244: 'argument': conversion from 'SAP_ULLONG' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
C:\node-rfc\src\Throughput.cc(138,5): warning C4244: 'argument': conversion from 'SAP_ULLONG' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
C:\node-rfc\src\Throughput.cc(208,52): warning C4244: 'argument': conversion from 'uint64_t' to 'double', possible loss of data [C:\node-rfc\build\sapnwrfc.vcxproj]
Hi,
I compiled the 1.0.6 release for Windows ia32 systems and I observed compilation warnings. These warnings didn't exist last week in the master branch. I don't see any problem at runtime so far.