What is the difference between int* and ptr in a dll call?

[martin 68]

If I use "ptr" as in the line which follows it works

dllcall("winspool.drv","int","GetDefaultPrinter","str",'',"ptr",DllStructGetPtr($namesize))

If I use "int*" or "dword*" it doesn't

dllcall("winspool.drv","int","GetDefaultPrinter","str",'',"int*",DllStructGetPtr($namesize))

According to msdn the parameter should be a pointer to a dword. I can create the struct as a dword, or as an int and the dllcall succeeds if I use "ptr" for the parameter type, but neither "dword*" nor "int*" works.

I thought both would work.

Can anyone explain the difference to me?

Edited June 5, 2008 by martin

[jwseek 0]

If I use "ptr" as in the line which follows it works

dllcall("winspool.drv","int","GetDefaultPrinter","str",'',"ptr",DllStructGetPtr($namesize))

If I use "int*" or "dword*" it doesn't

dllcall("winspool.drv","int","GetDefaultPrinter","str",'',"int*",DllStructGetPtr($namesize))

According to msdn the parameter should be a pointer to a dword. I can create the struct as a dword, or as an int and the dllcall succeeds if I use "ptr" for the parameter type, but neither "dword*" nor "int*" works.

I thought both would work.

Can anyone explain the difference to me?

dword* and int* are specified types of pointers. They allocate a specific amount of memory relative to those variable types. Creating a general "pointer" type to reference memory is much more likely to success as it's not forcing a specified type on unknown memory. This is why people hate working with pointers, they don't make a whole lot of sense.

[SmOke_N 199]

@Martin, I ran into this issue the other day myself.

@jwseek, if the param calls for a dword ptr, then the memory expected to be passed would that of a dword ptr I would think.

[jwseek 0]

@Martin, I ran into this issue the other day myself.

@jwseek, if the param calls for a dword ptr, then the memory expected to be passed would that of a dword ptr I would think.

Yeah, but a pointer to a dword and a dword pointer are different things. One simply points to a memory location that happens to contain a dword while the other is allocated memory the size of a dword variable. I think. I could be completely wrong.

[monoceres 183]

I'm just speculating but couldn't the keyword be reference?

Because like Valik pointed out to me in this topic pointers and references just isn't the same.

[evilertoaster 3]

@jwseek, if the param calls for a dword ptr, then the memory expected to be passed would that of a dword ptr I would think.

That's my understanding as well, and since 'ptr' is described as "a general pointer (void *)" it would make sense for it not to work, since void* and dword* are certianly not the same...

[martin 68]

That's my understanding as well, and since 'ptr' is described as "a general pointer (void *)" it would make sense for it not to work, since void* and dword* are certianly not the same...

Well what's been said so far hasn't helped my understanding. I thought a pointer was just an address where a variable was stored. In other words, in a 32 bit system passing a pointer is just giving a 32 bit value no matter what the pointer is for. The difference only is how that address is used to read the data (I thought). Since I'm wrong it would help the way I understand things if I knew what was being passed by "ptr" and what by "dword*" and what by "int*".

[Siao 0]

"ptr" is pointer - an address of whatever memory location you specify.

"int*" is internally controlled Int32 variable. You can set it to a number, and you can read it back from return array. Serves as poor man's ByRef.

Edited June 5, 2008 by Siao

[martin 68]

"ptr" is pointer, and address of whatever memory location you specify.

"int*" is internally controlled Int32 variable. You can set it to a number, and you can read it back from return array. Serves as poor man's ByRef.

Ah, so if I need too pass the C equivalent of &Var I should always use "ptr", and when I use "int*" then the receiving function is effectively directly controlling the variable? So "int*" is not like the C declaration int *var then?