AutoHotkey Community

OMFG
What happend to you Chris...

_________________

Yes, it makes sense, I came up with this hypothetical code:
I think the last parameter must be the return type, in some special DLLs it can be something other than 0/1 or true/false.

He was too bugged by a blue/violet monster...
Or more realistically, he got usable code!
Great news, all this is eagerly expected since a long time.

_________________
vPhiLho := RegExReplace("Philippe Lhoste", "^(\w{3})\w*\s+\b(\w{3})\w*$", "$1$2")

I wish it would be like Laszlo's Encode, Decode binary numbers

Thanks

The interface is actually planned to be simpler than that:

The code is very small; there is no string support like DllCall. Since there is no declaring of parameters or types (just the parameter count), it is up to the script to do any necessary conversions or type-casting (though that is unnecessary in most cases).

There is currently no ability to customize it, so perhaps the hard-coded support for a 32-bit return value is suitable for 99.9% of callbacks found in nature. I'll ask JGR.

Have you thought about internal hooks (with JGR code, again )?

_________________

Not yet.

PhiLho wrote:

In almost any callback function the return value will be some sort of 32 bit integer, which may represent a pointer, value, boolean, etc.
The only cases where it might conceivably be any different are if the callback uses a highly non-standard calling convention, in which case you couldn't use AHK for it anyway, or if the callback expects something to be returned on the FPU stack or something equally exotic, which this callback implementation does not support. I have never seen a callback function that fell into those two categories on windows, but it's possible I suppose.
In which case you'd have to write your own callback dll. If you did parameter conversion to a sensible calling convention, then you could probably have your callback dll call AHKs callback function and transmute the returned value.
This is not really an issue.

JGR

OK, fine for me. Do you think all parameters are 32bit too?
I saw implementations of callbacks that where just a bunch of template functions, with 1, 2, ... n parameters, all with the same type of parameters.

_________________
vPhiLho := RegExReplace("Philippe Lhoste", "^(\w{3})\w*\s+\b(\w{3})\w*$", "$1$2")

I think the stack is aligned on 4byte, so no real difference among char/short/long, but I may be wrong and not so sure about it when int64/double presents which I suppose rare anyway.

You are right.
I found in The Old New Thing : The history of calling conventions, part 3 a link to an MSDN page which leaded to the Argument Passing and Naming Conventions page which states:

64bit parameters are indeed rare, and can be handled as two 32bit parameters anyway.

_________________
vPhiLho := RegExReplace("Philippe Lhoste", "^(\w{3})\w*\s+\b(\w{3})\w*$", "$1$2")

I think that it wouldn't be monstrous to have this possibility... It would be certainly a means of extending the capabilities of Autohotkey, and to do things like Dock more easily...

Sure, however, what I meant by not sure was about the alignment size: still 4 byte or become 8 byte.
I heard that using 4byte impacts substantial performance penalty for Double, so some compliers uses dynamic stack alignment of 8byte, when Doubles are involved.

I tested and noticed a while ago that AHK's DllCall() still uses 4byte stack alignment even with int64 parameters (:not tested with Double, btw).
But, I can't really assume it with Callback as the stack is prepared by APIs/the system, although it's highly likely as the DllCall() worked flawlessly with 4byte alignment by AHK.

Monstrous? What is monstrous in hooks ? You can easily create malitious scripts in any language. You can easily kill a man with the spoon.

The fact is - if hooks are also internal, I don't see posibilities for more low level changes except for better struct support. The AHK would be extremely powerful, beyond competition. With hooks and after callbacks, any kind of OS manipulation will be possible. After all, AHK is automatition language, and it doesn't have many things to do in forign processes except simulating user input which is enough for small number of things and most of all, depend on 3td party application.

I doubt it would be much more complex then callbacks but I can easily be wrong.

_________________

In v1.0.46.17, A_UserName was fixed (it had been broken by v1.0.46.16).

It isn't Captain Hook that can find that hooking is monstruous. But ... may be a blue monster with long teeth can do marvelous things with a hook ?
Hooking is a tool. And like a knife, it can make a good steak or the page one of the Sun... It depends only on the way you use it. It was jeust a joke, majkinetor...