Questions about prototype information presentation

[sxzxs]

The prototype of the any class should be an empty string, but it is not in the image

[zero-plusplus]

Thanks for the report.

The prototype of the any class should be an empty string

I am not yet familiar with the v2 specs, what does the above mean?

Since these data are retrieved from the debugger, they should be in accordance with the v2 spec.

[sxzxs]

My interview is as follows：

I'm actually not familiar with the syntax rules, but the result is an empty string,

[zero-plusplus]

I have confirmed the issue.

I have not had time to check, but it is possible that I am confusing the <base> field with a simple Base field, which is causing this problem.

It may take some time to fix this issue as I am currently developing an extension to support AutoHotkey.

[zero-plusplus]

I just checked. I knew the issue was due to my confusing the <base> field with the Base field.

A fix for this issue has been added to tasks.
The actual fix will be delayed in favor of another extension as mentioned above.

[Lexikos]

The prototype of the any class should be an empty string, but it is not in the image

The prototype of the Any class should be a Prototype object, and it is in the image.

object.prototype.base.base

That is the Base of the Prototype of the Any class, and it is also in the image (Base: ""). This is a real property which can be evaluated in the script, and can be found by HasProp and similar.

MsgBox (Any.GetOwnPropDesc)(Any.Prototype, 'Base').Get.Name  ; ObjGetBase

There is no <base> shown for Any.Prototype because it does not have a base. This is not an error. <base> is not an actual property and is only returned by the debugger engine (part of AutoHotkey) if the object has a base object. It just happens that in v2, the only object that doesn't have a base object is Any.Prototype. It is much more common in v1.

If DBGP is used to query the <base> pseudo-property of an object which has no base, it returns an empty value of the DBGP type undefined, not string. This is consistent with the fact that <base> is not listed in the object's properties. (Anyway, it likely will not be listed at all in v2.1-alpha.10; see #324.)

There does not appear to be anything to fix.

[zero-plusplus]

Thank you.
I will close this Issues when I publish v2.0.0, which will resolve the <base> issue.