-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add section #9
Add section #9
Conversation
Done. |
Link added. Anything else? |
|
It is, nice catch.
Probably not, considering that C++ code highlighting might confuse people who expect the sample to be AHK code. If you think there should be highlighting though, feel free to add it - I'm not sure how to have it highlight C++.
I've escaped it, as well as the other one under Arrays.
I used "or similarly recent versions" to describe all these different version of AutoHotkey, since "and newer" implies hierarchy. |
OK. Should I merge now? |
If you don't see any other issues, that'd be great. |
Done. Thanks again! |
While writing on the DllCall page it comes to my mind it might possibly be better to split the "type mapping" part and put it either on the DllCall page or in a separate page. Also, what do you think of adding a more complex example? As I use MessageBox for DllCalls, I thought of MessageBoxIndirect. |
How about a page describing types in AHK, generally? Like Object/String/Integer/Float, and how these map to "machine" types?
I believe MessageBoxIndirect is a function as well. I think you meant MSGBOXPARAMS. In any case, I'm a bit busy lately but that would be a great thing to have. |
+1. I probably would put this right before DllCalls. |
1 similar comment
+1. I probably would put this right before DllCalls. |
I couldn't figure out how to reopen it either :/.
Anyways, I added a section about using A_PtrSize to calculate offsets portably, and added a contributor entry.