Statement cannot be just an expression with object problem.

[genius257]

Dim $Array = [1,2,3]
$oDictionary = ObjCreate("Scripting.Dictionary")
$oDictionary.Add("key", "value")
$oDictionary.Item("key") = $Array
MsgBox(0, "", $oDictionary.Item("key")[0])
$oDictionary.Item("key")[0] = 4

With the code above, I get the following error:

"C:\Users\genius257\Desktop\somename.au3"(6,32) : error: Statement cannot be just an expression.
$oDictionary.Item("key")[0] = 4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^

Now i know i could create a variable, assign the array, apply changes and assign the object item with the variable value.

But as i see it it's a lot of lines for something that should as far as my logic goes should make sense?

I would like to report a ticket, but i am not sure if I'm interpreting the AutoIt language wrong?

[jchd]

Sorry

Edited September 3, 2016 by jchd

[Jos]

You are seeing the au3check error. When disable au3check and run this script:

#AutoIt3Wrapper_Run_Au3Check=n
Dim $Array = [1,2,3]
$oDictionary = ObjCreate("Scripting.Dictionary")
$oDictionary.Add("key", "value")
$oDictionary.Item("key") = $Array
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $oDictionary.Item("key")[0] = ' & $oDictionary.Item("key")[0] & @CRLF ) ;### Debug Console
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $oDictionary.Item("key")[1] = ' & $oDictionary.Item("key")[1] & @CRLF ) ;### Debug Console
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $oDictionary.Item("key")[2] = ' & $oDictionary.Item("key")[2] & @CRLF ) ;### Debug Console
$oDictionary.Item("key")[0] = 4

I get

@@ Debug(6) : $oDictionary.Item("key")[0] = 1
@@ Debug(7) : $oDictionary.Item("key")[1] = 2
@@ Debug(8) : $oDictionary.Item("key")[2] = 3
"D:\Development\AutoIt3\programs\test\test.au3" (9) : ==> Illegal text at the end of statement (one statement per line).:
$oDictionary.Item("key")[0] = 4
$oDictionary.Item("key")^ ERROR

Does this work in VBS?

Jos

[genius257]

8 hours ago, Jos said:

Does this work in VBS?

I apologize, i should have checked in VBS. No, it appears to not cause any errors, but does not change the value.

Thanks for the time invested anyways.