DWORDs and integers can be cast to each other with no problems in DBP.
for example
myInt as integer
myDword as dword
myInt = 0xffffffff
myDword = myInt
print myInt ` Should print '-1'
print myDword ` Should print '4 294 967 295'
The DWORD datatype is simply an unsigned 32-bit integer.
A double integer is a signed 64-bit integer, but they aren't very well supported in DBP. As can be seen in your quote a standard 32-bit value can be written in hexadecimal form, where it ranges from 0 to ffffffff. A 64-bit value would be 0 - ffffffffffffffff.
In DBP, no, you won't need the double integers except in very special cases. The main reason for this is that they are automatically truncated to 32-bit values by most of the built-in functions anyway. The same goes for the double float.
Quote: "OH! And I must ask, what are the bitwise operators limited too? I was about to use a bunch of them for matching values together."
Nothing, really; all data is stored as bits (which, as the name suggests is what these operators operate on), just interpreted differently. But in DBP it seems they can only be used on integers and DWORDs (the same as the built-in dynamic memory functionality).
With some tricks you can convert hexadecimal values to floats as well by the way, and bytes and WORDs are just shorter unsigned integers so that should be no problem.
"Why do programmers get Halloween and Christmas mixed up?" Because Oct(31) = Dec(25)