The compiler warning disappeared with the latest build (#371 win32) - thank you, dkl - , but the problem mentioned by fxm seems to be not fixed yet:
Code: Select all
Function getB() As Boolean
Dim result As boolean
Dim A As boolean = TRUE
result = A AndAlso getB()
Print A AndAlso getB() 'output: 0
Print result 'output: false
The first print results in a "0" output instead of "false". Removing/adding outer parantheses does not change anything.
I'm also totally aware that I'm using a build of work-in-progress code, not a final release build. I just want to report/(document) suspective behaviour I've encountered. Maybe there are some issues that are already known, but I've simply not heard about them yet.
I've just noted that the build numbers on 32/64 Windows are NOT the same (at the same Date).
32bit == 0367 == today (last night)
64bit == 0368 == today (last night)
so one should NOT rely to much on the build # alone!
Yes that's right. It was only a nice coincidence that the win32/win64 build numbers were aligned for a longer period of time. In fact each platform build is independant from the others, therefore a changelog exists for each platform. Maybe I can modify the process to synchronize the build numbers, but Jenkins (the CI server I am using for the builds) is not designed to have multiple builds accessing the same checkout, but rather each build using its own checkout (yet, there do exists plugins/process patterns to model that behaviour too).