[RESOLVED] Why do you still use datatype Long for pointers?

[OlimilO]

To me, OlimilO is operating under the delusion that Microsoft will someday release a 64 bit verions of VB6, which, the rest of us know, is clearly never going to happen.

Am I missing something? who is talking about "M$ bringing up something"? At least not me. Though we do have VBA-x64 as you know it is made by Microsoft. Nowadays there is twinBasic a perfect contender to VB6, do you expect more?
I must confess many years ago I was planning to write my own "VB-compiler-c-translater" but since twinBasic is making great strides . . .

... porting to 64 bit VBA is MUCH more involved that just changing all the pointers from Long to LongPtr.

Nope it is not! If you would only try it, you would see that it is in fact more easy than it looks.
But OK I must confess, it takes practice to get the hang of it

Next, OlimilO will be getting all upset with us because we don't embed the 64 bit API calls within our VB6 application as #IF conditional compilation statements.

Just read the tutorial, in fact I say that you don't have to use so much "#IF" statements, in fact you can get rid of so much #IF statements

I will agree that using some kind of "p" Hungarian notation is nice when we actually have a pointer. But even that is a personal preference.

I am not talking about personal preference. I was talking about the names of function parameters in the winapi-functions. This names are provided by microsoft, no personal preference there.
But I am glad you bring this up, whenever you see a parameter name beginning with "lp*" this means "LongPtr" often used for string-parameters.

When considering VB6 and VBA jointly, 99% of the time, I'm porting VBA code to VB6, not the reverse.

Yeah I don't know any of your business. But could it be, that the reason for this is, because the code does not run in VBAx64 because someone used Long instead of LongPtr?

So, using Long for pointers makes perfect sense to me, and anything else is someone tilting at windmills trying to dictatorially impose their 'brand' of coding on the rest of the world.

Come on, now you are getting pathetic