Does uint64 exist in AutoIt or only int64?

[c.haslam]

The context is a DLL struct tag with a uint64 element.

[genius257]

Hi @c.haslam

You should check the documentation before asking: DllStructCreate

First column (type), 16th row (if you count the header), between INT64 and PTR

[AspirinJunkie]

In DllStruct* yes - but not in AutoIt itself - right?
This means that the variables are correctly present in the structure as UInt64, but when used in AutoIt they are treated as Int64.
Therefore, there should be problems if you have read out values that only exist in the UInt64 area.

I can't test this at the moment, because I don't have AutoIt available here.

[RTFC]

Search the forum first:

 

[c.haslam]

Thank you all for both your helpful (and less than helpful) answers. By "in AutoIt" I meant "in an AutoIt variable". The Help for DllStructCreate() infers that uint64 is handled properly, because it does not say that it isn't.  I did search the forum, and found a discussion of unsigned 64-bit integers from when AutoIt was at v. 3.3.3. It shows that AutoIt did not handle uint64 9 years ago. I was wondering whether this deficiency had been fixed.

It now appears that I have the answer.

Local $tag = 'uint64'
Local $tStruct = DllStructCreate($tag)
DllStructSetData($tStruct,1,0xffffffffffffffff)
MsgBox(0,'',DllStructGetData($tStruct,1))

in AutoIt v. 3.3.15.0 shows -1, so it appears that the AutoIt variant has no uint64 subtype. Further, I suspect that AutoIt will never be able to handle uint64, that is other than being written as an element of a struct.

I note particularly Tekk's work-around.

Edited January 23, 2018 by c.haslam

[jchd]

uint64 and int64 are stored the same way. All AutoIt is uncomfortable doing is proper unsigned uint64 arithmetic and comparisons or display as unsigned integer.

[c.haslam]

jchd,

Thanks for the clarification. Your _VarDump() code (and of course, ideas) are incorporated in my cDebug.au3, now in Example Scripts. I had the nested array stuff working (and being used by me) to the Console, Clipboard and a MsgBox, and had been using it for some years. All the non-numeric, non-string stuff is thanks to you! So really cDebug.au3 has several authors -- who are properly credited.