[v2.0.11; v2.1-alpha.8] Command Syntax doesn't work when there are brackets in the command?

[iseahound]

[Moderator's note: Topic moved from Bug Reports.]
Not sure if it's a bug when the parenthesis are omitted when the function call has []

Code: Select all

a := []
a.push "test"
MsgBox a[1]

m := Map()
m['a'] := []
m['a'].push "test"
MsgBox m['a'][1]

[just me]

If it isn't a bug a 'Common source of confusion:' note should be added to the docs.

(I always voted to remove the 'command syntax' as far as possible in v2!)

[guest3456]

(I always voted to remove the 'command syntax' as far as possible in v2!)

+1
when i was initially building the v2 converter i would never convert to the command syntax variant, to discourage users from using it. not sure what other contributors have done since

[lexikos]

Let go of the past; there is no command syntax in v2. Command syntax was never usable with methods in v1.

a.push "test" is a method call statement.

Parentheses can also be omitted when calling a method in this same context, but only when the target object is either a variable or a directly named property, such as myVar.myMethod or myVar.myProp.myMethod.
Source: Scripting Language | AutoHotkey v2

If it isn't a bug a 'Common source of confusion:' note should be added to the docs.

Exactly where and how might a user find such a note? The "Function Call Statement" section (quoted above) already explicitly states the conditions under which parentheses can be omitted. Is there some other part of the documentation which might lead the user to believe they can call a method without parentheses?

[V2User]

Yes, command syntax never contains object with a method.

[just me]

If the return value of the function is not needed and the function name is written at the start of the line (or in other contexts which allow a statement, such as following else or a hotkey), the parentheses can be omitted.

IMO, all of that can be should have been eliminated in v2 to avoid confusion. But that did not happen, It therefore makes no sense to continue discussing it.

To avoid such errors you've always the option of not using the can bes.

[V2User]

I think it might be a pity for V2 that it hasn't "kill" all.

[lexikos]

IMO, all of that can be should have been eliminated in v2 to avoid confusion. But that did not happen, It therefore makes no sense to continue discussing it.

We weren't discussing it, were we? I didn't bring it up.

To avoid such errors you've always the option of not using the can bes.

I completely agree.