AutoHotkey Community

Closure.Prototype.__Delete := this => OutputDebug('closure dctor: ' ObjPtr(this) '`n') ff() { a := 0 b := f2 OutputDebug('f1: ' ObjPtr(f1) '`n') OutputDebug('f2: ' ObjPtr(f2) '`n') f1() ; b := 0 ; Free variables was not released during closure destruction. f1() { b() } f2() { a := 1 } } ff()

I fixed it yesterday.

The downloaded zip package contains both 32 and 64 bits, doesn't yours?

The registry has different views in 64-bit and 32-bit, and if you run this code with AHk_l 32-bit, you'll get the same error.

@TAC109

In my tests, ScriptGuard2 also works for ahk_h.

No, it is same as ahk_l.

There are only a handful of conflicts, and I don't think a lot of code needs to be rewritten.

ahk_h has additional classes and class methods, and in this respect conflicts with some ahk_l scripts, which is unavoidable.

Why compile with ahk_h when you have been using ahk_l all along?

The library you are trying to include conflicts with the built-in JSON class in ahk_h. If there are no special requirements, the JSON library can be removed.

You may need to update ahk2exe.
download/file.php?id=25410

You can just add an __Item property to the prototype of the class you pass to StructFromPtr (explicitly or via class definition). For now, you also have the option of adding properties to the object returned by StructFromPtr. Yes, it can be done that way. The first option is more convenient to use,...

You can create a class dynamically.

If __value returns 0 for a null pointer, there will be ambiguity when the type is int*.
The current solution also makes it impossible for pointer types to be used as arrays, like p[0], p[1].

Should the __value.get of the pointer class be removed, so that null pointers can be retrieved?

Fixed in the next version.

This should be a bug that clones non-value properties.

https://www.autohotkey.com/docs/v2/lib/Object.htm#OwnProps wrote: If two variables were specified, the enumerator attempts to call the property's getter to retrieve the value.
If the getter requires parameters, the property is skipped.
If Obj itself does not define a getter for this property, it is skipped.

lexikos wrote: So ¥ can't appear in an NTFS filename, and must only be a path separator (or invalid).

On my computer, ¥ can be used as the NTFS file name. Is it backslash \ that appears as ¥ in a specific font?

@lexikos
Is it necessary for a class to allocate memory when it has no typed properties?

Using OutputDebug in debugging.
Output to stdout FileAppend(str '`n', '*') at any time.