Bitwise not Topic is solved

[nnnik]

[Update by Lexikos: v2.0-a083 changes bitwise-not to always treat the number as 64-bit.]

Bitwise-not (~): This inverts each bit of its operand. If the operand is a floating point value, it is truncated to an integer prior to the calculation. If the operand is between 0 and 4294967295 (0xffffffff), it will be treated as an unsigned 32-bit value. Otherwise, it is treated as a signed 64-bit value. For example, ~0xf0f evaluates to 0xfffff0f0 (4294963440).

I think that starting V2 Bitwise not should always treat the operand as a signed 64 bit value.

[lexikos]

Why?

[nnnik]

I expected bitwise not to do exactly that in V1 already since I think that AHK Integers are mostly treated as 64 bit integers.
To me it would be easier to understand, or rather it seems more consistent.