Re^2: Bitwise & stopped working?

Thanks muchly for the suggestions. It seems that executing the script whilst running a debug build via Visual Studio caused ActiveState's Perl to run rather than the version I was supposed to be using, indicating a path issue. This explains the sudden failure of bitwise AND.

The notion that $hash is being converted to float appears to stand up; by changing the AND to "% 4294927296", the script works properly in both versions of Perl and all is well in my world again. :D

Update: Oh, and to further show that it was a float issue, the ActiveState Perl was 32-bit, the version I normally use is indeed a 64-bit build.

Comment on Re^2: Bitwise & stopped working? Download Code

Replies are listed 'Best First'.
Minor nitpick by proceng (Scribe) on May 12, 2010 at 22:44 UTC
It seems that executing the script whilst running a debug build via Visual Studio caused ActiveState's Perl to run rather than the version I was supposed to be using, indicating a path issue. In the future, when something "suddenly stops working" and "I haven't changed anything", look to see if you actually have changed something (like the processing environment).	[reply]
Re: Minor nitpick by Krokus (Novice) on May 14, 2010 at 04:46 UTC
In the future, when something "suddenly stops working" and "I haven't changed anything", look to see if you actually have changed something (like the processing environment). That is certainly good advice and indeed, in my original post I stated that my first thought was, "well, it must be a result of something I did elsewhere...". In my defense, however, I was not aware that, of the two builds of Perl I had available, one was a 32-bit build and one was a 64-bit build. As well, I had been debugging my application for several hours beforehand with no issues from my scripts. I don't know how my paths suddenly got changed in the middle of a debugging session. I'm still rather bewildered about that. :)	[reply]