Custom Query (3917 matches)

#cs
	AU3Check, false error, For $i[array] = ..

	C:\..\test.au3(12,7)) : ERROR: syntax error
	For $i[
	~~~~~~^

	AU3Check (1.54.14.0) (AutoIt3: 3.3.0.0)
	AU3Check (1.54.17.0) (AutoIt3: 3.3.1.2)
#ce
Dim $i[2]
For $i[0] = 1 to 2
	For $i[1] = 1 to 2
		ConsoleWrite('$i[0]='&$i[0]&', $i[1]='&$i[1]&@CRLF)
	Next
Next

;~ >"C:\..\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /run /beta /ErrorStdOut /in "C:\CODE\_WORK_\Dev_AutoIt\_TEST_\arrayToString\bedug.au3" /autoit3dir "C:\CODE\AutoIt3\beta" /UserParams    
;~ +>13:47:30 Starting AutoIt3Wrapper v.2.0.0.1    Environment(Language:0409  Keyboard:00000409  OS:WIN_XP/Service Pack 3  CPU:X86 OS:X86)
;~ >Running AU3Check (1.54.17.0)  from:C:\CODE\AutoIt3\beta
;~ C:\CODE\_WORK_\Dev_AutoIt\_TEST_\arrayToString\bedug.au3(12,7) : ERROR: syntax error
;~ For $i[
;~ ~~~~~~^
;~ C:\..\bedug.au3 - 1 error(s), 0 warning(s)
;~ !>13:47:30 AU3Check ended.rc:2
;~ >Running:(3.3.1.3):C:\..\AutoIt3\beta\autoit3.exe "C:\..\bedug.au3"    
;~ $i[0]=1, $i[1]=1
;~ $i[0]=1, $i[1]=2
;~ $i[0]=2, $i[1]=1
;~ $i[0]=2, $i[1]=2
;~ +>13:47:32 AutoIT3.exe ended.rc:0
;~ +>13:47:34 AutoIt3Wrapper Finished
;~ >Exit code: 0    Time: 3.880

I've run into a situation where a Scripting.Dictionary object method call is changing variable types within an AutoIt array, simply by referencing them.

func testDictionary($a)
	local $d=objCreate('Scripting.Dictionary')
	for $i=0 to ubound($a)-1
		$d.add($i,$a[$i])
	next
	return $d
endfunc

local $aTest[2]=[false,true]

msgbox(0,default,$aTest[0]) ; displays false
msgbox(0,default,$aTest[1]) ; displays true

local $ignore=testDictionary($aTest)

msgbox(0,default,$aTest[0]) ; displays 0 instead of false
msgbox(0,default,$aTest[1]) ; displays 1 instead of true

Apparently, when the $d.add() call references $a[$i], it's also converting booleans to numbers within the array itself, and those changes are reflected in the original array afterwards.

In this example, the problem goes away if I change the top line to:

func testDictionary(const byRef $a)

I've verified that this bug is present in the 3.3.1.3 beta as well.

In a Switch statement, a Case with a negative number gets separated when run through Tidy from within Scite.

Switch $x
Case -1
    ; Whatever happens next
EndSwitch

becomes

Switch $x
    Case - 1
        ; Whatever happens next
EndSwitch