AutoHotkey Community

To me, enum[k]:=v appears elegant. We can think of obj/enum as the conjugate pair under the time reversal, i.e., obj/enum propagates forward/backward in time, and obj/enum[k]:=v remains a valid form under reversing time. At any rate, IMO, there is no need to disallow it. Let the user decide what to use.

I though about it, but it can be achieved in script level easily, too.

We do not provide a library that contains most common used scripts like AutoIt does (though we have many nice scripts in this forum or the wiki), but I think it may be good to do. This can avoid adding these trivial works to the core and bloating its size.

I'm trying to call a user define function "newEntry" thusly:
newEntry doesn't take any parameters. This is by design (think of it as a constructor w/ no parameters).

My first problem is when I do the simple syntax above, it doesn't invoke anything.

The second problem is if I spice things up a bit by doing:.. my function get's invoked, but it's not passing the object reference into the call. The documentation says "When called, the parameter list contains a reference to the target object, followed by the parameters of the get, set or call operation."

Here is my full code:


Appreciate any help!!!

Thanks,
Shawn

_________________
AHK_H (2alpha) AHF TT _Struct WatchDir Yaml _Input ObjTree RapidHotkey DynaRun

I agree, but in this case I think it really helps the usability of the function. Even if you can remember the flags, some other user reading your code probably won't. If I were to provide a user-friendly wrapper, I'd have to recommend everyone use it over the built-in function...
Check the context - that only applies to meta-functions, i.e. __Get, __Set and __Call. Similar behaviour is briefly mentioned for other methods defined in base under Extensibility. Essentially, an object reference is passed only if/because the function is defined/called indirectly through a base object.
This should also work:
NOT this:

Noticed that the RegexMatch in position mode returns "1" for non-matched patterns when in standard AHK it returns "0".



Using "AutoHotkey_L".


Using normal Autohotkey.



Is this intended or possibly a bug of some sort?

It's a bug caused by some Unicode-related changes. Thanks for reporting it.

The comparison of features link in version history seems dead: http://www.autohotkey.net/~Lexikos/AutoHotkey_L/docs/LvsU.htm.

Thanks, I had removed the file when I revised the documentation since most of it was rewritten in more detail elsewhere. (But there is no comparison elsewhere since jackieku now steers users towards AutoHotkey_L.) I've restored it and also updated the documentation download, which hadn't been updated last time due to an error in my update script.

i gues this will never be supported:
i can never directly ask the value of !ut but i need to loop to find it.
wich is out of the question for me.
this is my firs array tryout.
Lexikos, thanks for all the hard work you put in it

_________________
Stopwatch emdkplayer
the code i post falls under the: WTFYW-WTFPL license

_________________

Recommended: AutoHotkey_L
Basic Webpage Controls

LOL

Works for me to, had a typo, fixed it in the example but not in my code

_________________
Stopwatch emdkplayer
the code i post falls under the: WTFYW-WTFPL license

Ok I get it. So for direct calls, is there a "this" or "me" variable that gets set?

(Although I'm getting the feeling this is a silly question, that methods should be set in the .base, and data belongs in the specific instance of the class)

Thanks,
Shawn

No. If there was, there'd be no need for the differing behaviour, and no need to pass it as a parameter. (I chose the current approach for performance and practicality reasons.)
No.
That's about it. My view is that when a value stored in an object is "called" directly, there's nothing inherently special about it and no reason to alter the parameter list. On the other hand, base exists to define the behaviour of the object, so functions called via this mechanism must be designed to accept (and probably require) a reference to the original object.

Of course, each object can have its own unique base if necessary. Alternatively, the behaviour of individual "methods" can be controlled by calling objects instead of function names:
There's another example of this technique under "Objects as Functions" in the docs.