AutoHotkey Community

Safer?, I agree. Faster?, I don't know. Simpler?, I disagree.
I chose ++ptr not because I didn't know *(ptr+1) is safer. I did it just because ++ptr looked simpler and elegant, at least symbolically. So, I won't change it unless it's broken. Of course you can change it as whatever you like.

I understand. But I'm doubtful how many users would take the trouble to go to MSDN before using the helper functions.
They may ask: what kind of name are these, MultiByteToWideChar and WideCharToMultiByte? They really don't mean much. So, I chose Ansi2Unicode etc, even if they are ambiguous: Ansi, it's not only ANSI, it can be OEM, or even MAC codepages or UTF-7 or UTF-8. And UTF-16 is not the only Unicode encoding. However, it would convey the actual purpose of the function more clearly. (As you probably guessed already, 2 for To, 4 for From here) BTW, I was tempted to use Ansi2Wide etc, but I decided not.

Regarding CreateObject and GetObject, as a matter of fact, I hesitated a little between them and CoCreateObject (:not CoCreateInstance) and CoGetObject. The reason was that I was afraid of that it could lead name collisions when AHK implements COM fully. AHK would want to use the names after VB like I did. But, after surveying the naming conventions of AHK, I concluded it's rather unlikely. It's likely to use the names like ObjCreate and ObjGet as AutoIt did. So, I took the names from VBS.

Anyway, if you have better names, please let me know.

If you are afraid of nameclashes use a decent prefix. COM_ ?

There is an item in the pre-release test battery to prevent evaluation order from changing. If it ever does change, I intend to log it in the changelog.

I think I mentioned this in some other topic, but maybe it got lost in the shuffle.

Why not add a sentence to the Help, saying that all operands are evaluated, except in short-circuit logic expressions, and in left-to-right order (next to "Operators of equal precedence such as multiply (*) and divide (/) are evaluated in left-to-right order unless otherwise specified"). It looks like many scripts posted to the Forum rely on it. (People don't seem to be taught any more about good programming styles.) This little change in the documentation would make those scripts valid (but still of bad style).

I'd like to do it, that's also majkinetor suggested to do. But, there is a problem. What about Ansi2Unicode or Unicode2Ansi? Should they be prefixed with either COM_ or API_?
Actually Unicode2Ansi in CoHelper.ahk used to be secialized to be used in COM only: it was designed to receive only a pointer to the unicode string, not a variable for a string. So, it should be prefixed by COM_.
But, now I've changed it to receive both a pointer and a variable as ByRef (:there is still a chance to go wrong, for example, if the unicode string starts with U+3939 U+3939 U+0030...). So, should it be now prefixed with API_?

What about DecodeInteger and EncodeInteger?

Any suggestion?

So what's the deal on the COM naming conventions?

Will these names hold, when COM is introduced into AHK?

Speaking of which, this whole AHK and COM is smoking hot, so when/what release will AHK offically go COM???

Also, if I had a vote, I would go with the JScript naming conventions for COM/OLE. This way, you do not copy AutoIt, but have naming conventions that are recognized.

AutoHotkey is not "in line" with Visual Basic and VBScript programming style. So JScript type names may be better for AutoHotkey. AutoHotkey and JScript, are more in line with C "programming style".

Oppsss... Jscript language reference, to see what names they used.

http://msdn2.microsoft.com/en-us/library/hbxc2t98.aspx

You can also download both JScript's Help CHM and VBScript's Help CHM from

http://download.microsoft.com/download/ ... ptHelp.msi

So that more people find out about this topic, I've linked to it from the DllCall page. Its "related" section now reads: "Component Object Model (COM): It is possible to use COM via DllCall. There is a series of helper functions at http://www.autohotkey.com/forum/topic16631.html.

Sean, I hope you don't mind, but I also added a link in the topmost post here that points to one of your topics that uses COM Helper. Feel free to revise it as you see fit.

Thanks.

Of course not. Thanks for adding the link.

2 Chris
I beleive that it is much better to add wiki section where I collected almost all important things done with COM including this one, in a much more organised way, including examples where appropriate. On the wiki are also references to the forum

http://www.autohotkey.com/wiki/index.ph ... M_Wrappers

_________________

Thanks; I've updated the DllCall page to use that link.

How can I translate this JS-Code to AHK?

_________________
Tekl

I don't have a iTunes.