PureBasic Forums - English

I agree that the x86 version produces the less-correct result; however, that doesn't change the picture much. Many Windows constants (of those in common use, at least 60 supplied in the PureBasic definitions) use the high bit of a longword (that is, are negative longwords): when such constants are ...

I agree that the difficulty varies based on the manner in which a constant is used; however, this doesn't make it less of an issue. The behavior isn't documented and is difficult to detect: in the code below, note that the x86 behavior matches the x64 behavior except when the variable is directly ...

Yes, a defect. Try:

#MyConstantA = $81010000
#MyConstantB = -2130640896 ;(same value in decimal notation)
Debug Hex(#MyConstantA, #PB_Long)
Debug Hex(#MyConstantB, #PB_Long)

YOU ARE REINFORCING MY POINT! A longword constant defined via hexadecimal notation does not behave the same as a longword ...

In versions 5.71 and 5.70 of the 64-bit Windows editions of PureBasic, a negative longword constant which is defined via hexadecimal notation is treated as a (positive) quadword (that is, as an "integer" on the platform). This can cause significant confusion!! For example:

EnableExplicit ...

Currently, a link error is displayed in a fixed-size popup window and will typically be truncated (due to the display of innocuous warnings regarding variant segment attributes). It would be helpful if the complete text of any link error was displayed in the log region of the IDE.

Background: In ...

It would be great to be able to tag an IF as a likely branch -- perhaps LikelyBranchingIf -- causing the compiler to emit the static-branch-likely-hint prefix (0x3E) to the conditional emitted in the assembly code. Since there is a work-around (albetit rather ugly), this is a low-priority wish.

The ...