Arrays - Revision history

Nine: /* Comparing Arrays */

2024-01-13T13:33:05Z

Comparing Arrays

← Older revision		Revision as of 13:33, 13 January 2024
Line 286:		Line 286:
	Local $Array1[3] = [1, 2, 3]		Local $Array1[3] = [1, 2, 3]
	Local $Array2[3] = [1, 2, 3]		Local $Array2[3] = [1, 2, 3]
	Local $Array3~~[4]~~ = ~~[1, 2, 3, 4]~~		Local $Array3 = $Array1

	~~If $Array1 == $Array2 Then~~ ConsoleWrite("1.) $Array1 ~~is equal to~~ $Array2~~! which might be correct in some sense."~~ & @LF); while they contain the same data, the comparison does not work.		ConsoleWrite("1) " & ($Array1 = $Array2 ? True : False) & @LF)
			; while they contain the same data, the comparison does not work.

	~~If $Array1 == $Array3 Then~~ ConsoleWrite("2.) $Array1 ~~is equal to~~ $Array3~~! which is incorrect."~~ & @LF); even though they~~'re different in size~~, ~~it's incorrectly determined that they're equal~~.		ConsoleWrite("2) " & ($Array1 = $Array3 ? True : False) & @LF)
			; even though they are referencing the same array, the comparison does not work.
	</syntaxhighlight>		</syntaxhighlight>

	~~I have the impression that such comparisons compare the memory address of the~~ arrays ~~instead of~~ the array ~~elements values. And the~~ addresses are always different for different arrays. You have to instead, compare all elements one after the other. It might be a good idea to first compare array sizes if that can vary for both the compared arrays!		Comparing arrays will always return false since the array memory addresses are always different for different arrays. You have to instead, compare all elements one after the other. It might be a good idea to first compare array sizes if that can vary for both the compared arrays!

	The next example creates an array from user input and then compares elements from a 1D Array to the first column of a 2D array to return the matches as words.		The next example creates an array from user input and then compares elements from a 1D Array to the first column of a 2D array to return the matches as words.

Skysnake at 11:24, 1 December 2017

2017-12-01T11:24:54Z

← Older revision		Revision as of 11:24, 1 December 2017
Line 439:		Line 439:

	AutoIt features a large list of [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions (UDF)], among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions Reference].		AutoIt features a large list of [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions (UDF)], among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions Reference].
	[[Associative Arrays]]		<br />
			<br />
			An associative array is an array where the keys (index numbers) are string instead of integer, as they are in AutoIt. See the [[Associative Arrays]] page for more information.
	[[Category:Tutorials]]		[[Category:Tutorials]]

Skysnake at 08:58, 28 November 2017

2017-11-28T08:58:26Z

← Older revision		Revision as of 08:58, 28 November 2017
Line 439:		Line 439:

	AutoIt features a large list of [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions (UDF)], among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions Reference].		AutoIt features a large list of [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions (UDF)], among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions Reference].
	[~~http://www.autoitscript.com/autoit3/docs/assocarray.htm~~ Associative Arrays]		[[Associative Arrays]]
	[[Category:Tutorials]]		[[Category:Tutorials]]

Skysnake at 08:56, 28 November 2017

2017-11-28T08:56:35Z

← Older revision		Revision as of 08:56, 28 November 2017
Line 439:		Line 439:

	AutoIt features a large list of [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions (UDF)], among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions Reference].		AutoIt features a large list of [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions (UDF)], among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions Reference].
			[http://www.autoitscript.com/autoit3/docs/assocarray.htm Associative Arrays]
	[[Category:Tutorials]]		[[Category:Tutorials]]

Skysnake: /* Comparing Arrays */

2017-08-30T14:47:15Z

Comparing Arrays

← Older revision		Revision as of 14:47, 30 August 2017
Line 294:		Line 294:

	I have the impression that such comparisons compare the memory address of the arrays instead of the array elements values. And the addresses are always different for different arrays. You have to instead, compare all elements one after the other. It might be a good idea to first compare array sizes if that can vary for both the compared arrays!		I have the impression that such comparisons compare the memory address of the arrays instead of the array elements values. And the addresses are always different for different arrays. You have to instead, compare all elements one after the other. It might be a good idea to first compare array sizes if that can vary for both the compared arrays!

			The next example creates an array from user input and then compares elements from a 1D Array to the first column of a 2D array to return the matches as words.
			<syntaxhighlight lang="autoit">
			; sample number string split and convert to words
			; uncomment the ConsoleWrite and _ArrayDisplay lines to see what it does
			;# some includes
			#include <Array.au3>

			;# some variables

			;Create 2D array to display
			Local $aWords[10][2] = [[0, 'nil'] _
			, [1, 'one'] _
			, [2, 'two'] _
			, [3, 'three'] _
			, [4, 'four'] _
			, [5, 'five'] _
			, [6, 'six'] _
			, [7, 'seven'] _
			, [8, 'eight'] _
			, [9, 'nine']] ; :)

			;~ _ArrayDisplay($aWords)

			; the order of the sample digits is to show that the comparison below is accurate, from left to right
			Local $Originalinput = InputBox("Type a number", "A number?","97524601")

			Local $userinput = $Originalinput ; pass the orginal input to a second var
			; now parse the userinput to that we know what was submitted, then repeat in words
			; first strip all white space
			$userinput = StringStripWS($userinput, 8)

			If StringIsDigit($userinput) Then ; continue

			; now get the length of the string
			Local $islong = StringLen($userinput)

			; make an array with size = length to insert items into
			Local $aInput[1] ; create blank one dimensional array
			;~ _ArrayDisplay($aInput)
			; eat the string one digit at a time :)
			Local $oneleft
			For $i = 1 To $islong Step 1
			$oneleft = StringLeft($userinput, 1)
			ConsoleWrite("$oneleft: " & $oneleft & @CRLF)
			$userinput = StringTrimLeft($userinput, 1) ; make the $userinput one shorter on each loop
			_ArrayAdd($aInput, $oneleft, 1)
			Next
			;~ _ArrayDisplay($aInput)
			; now write out what the user typed in words

			;~ ConsoleWrite("How long is the string: " & $islong & @CRLF)
			; compare the user input to our defined array
			For $k = 0 To $islong Step 1
			For $j = 0 To (UBound($aWords) - 1) Step 1
			;~ ConsoleWrite("Compare $j " & $aWords[$j][0] & " to $k " & $aInput[$k] & @CRLF)
			If $aWords[$j][0] == $aInput[$k] Then
			MsgBox(0, "Number to word", $Originalinput&@CRLF&"User typed "& $aInput[$k]& @CRLF & $aWords[$j][1] & @CRLF,1)
			EndIf
			;~ ConsoleWrite("For... Next inner loops: " & $k & @CRLF)
			Next
			;~ ConsoleWrite("For... Next outer loops: " & $j & @CRLF)
			Next

			EndIf ; if its not digits, skip

			</syntaxhighlight>

	== Multi Dimensional Arrays ==		== Multi Dimensional Arrays ==

Melba23 at 08:56, 23 November 2015

2015-11-23T08:56:34Z

← Older revision		Revision as of 08:56, 23 November 2015
Line 354:		Line 354:
	== Arrays in Arrays ==		== Arrays in Arrays ==

	You may save an array in an array element (item). ~~The thing is,~~ there is ~~no way to directly access~~ that ~~array stored in the element~~. ~~You have~~ to ~~go through a variable~~ to ~~get access~~ to ~~the embedded array which may~~ make your code ~~overly complicated and difficult to debug~~.		You may save an array in an array element (item). Remember that there may be issues if you pass an array containing arrays into a function and the embedded array is changed inside that function. So, as a general rule, try not to embed arrays within arrays unless you absolutely need to and are prepared to do rigorous testing to make sure your code will always work as expected.

	~~Remember that there may be issues if you pass an array containing arrays into a function and~~ the embedded ~~array is changed inside that function. So, to conclude this, try not to embed~~ arrays ~~within arrays unless you absolutely need to and are prepared to do rigorous testing to make sure your code will always work as expected.~~		You can access the elements of these embedded arrays directly (note the additional () required):

	~~That said, here is an example.~~

	<syntaxhighlight lang="autoit">		<syntaxhighlight lang="autoit">
	Local $~~arr~~[3]		Local $aContainerArray[2]
	Local $a1[3] = [2, "a1-1","a1-2"]		Local $aInternalArray_0[2] = ["Internal-0-0","Internal-0-1"]
	Local $a2[3] = [2, "a2-1","a2-2"]		Local $aInternalArray_1[2] = ["Internal-1-0","Internal-1-1"]
	$~~arr~~[1] = $a1		$aContainerArray[0] = $aInternalArray_0
	$~~arr~~[~~2] = $a2~~		$aContainerArray[1] = $aInternalArray_1
	~~$arr[0] = 2~~
	~~Local $dumy~~

	~~For $i =~~ 1 ~~to $arr[0~~]
	~~$dumy~~ = $~~arr[$i]~~

	~~If IsArray($dumy) Then~~		ConsoleWrite("1 element of InternalArray_0: " & ($aContainerArray[0])[1] & @CRLF)
	~~For $j = 1 to $dumy[0]~~		ConsoleWrite("0 element of InternalArray_1: " & ($aContainerArray[1])[0] & @CRLF)
	ConsoleWrite("$i:=" & $~~i & ", $dumy~~[~~" & $j & "~~]~~:=" & $dumy~~[$j] & @LF)
	~~Next~~
	~~Else~~
	ConsoleWrite("~~!>Oops!, What happened? Expected an array!~~" & @LF)
	~~EndIf~~
	~~Next~~
	</syntaxhighlight>		</syntaxhighlight>

JLogan3o13 at 17:26, 20 October 2014

2014-10-20T17:26:56Z

← Older revision		Revision as of 17:26, 20 October 2014
Line 1:		Line 1:
	An '''array''' is a [[Data_Structures\|data structure]] which stores elements (variables) aligned in a computer's memory. Arrays are referenced by an [[identifier]] (variable name) and an index specifying a desired element.		An '''array''' is a [[Data_Structures\|data structure]] which stores elements (variables) aligned in a computer's memory. Arrays are referenced by an [[identifier]] (variable name) and an index specifying a desired element. The array concept seems complex but the concept can be easily grasped. Why are arrays so important? The array is a fundamental data structure found in most programming languages.

	The array concept seems complex but the concept can be easily grasped. Why are arrays so important? The array is a fundamental data structure found in most programming languages.

	This tutorial targets people who are beginners. To understand how arrays work, it is imperative to try out and modify the provided samples. Make sure that each concept is understood before the next concept is attempted. This tutorial assumes the use of the SciTE editor. There is a minimal version of SciTE included in the latest stable release of AutoIt (version 3.2.0.1 and above).		This tutorial targets people who are beginners. To understand how arrays work, it is imperative to try out and modify the provided samples. Make sure that each concept is understood before the next concept is attempted. This tutorial assumes the use of the SciTE editor. There is a minimal version of SciTE included in the latest stable release of AutoIt (version 3.2.0.1 and above).

JLogan3o13 at 17:26, 20 October 2014

2014-10-20T17:26:31Z

← Older revision		Revision as of 17:26, 20 October 2014
Line 1:		Line 1:
	An '''array''' is a [[Data_Structures\|data structure]] which stores elements (variables) aligned in a computer's memory. Arrays are referenced by an [[identifier]] (variable name) and an index specifying a desired element.		An '''array''' is a [[Data_Structures\|data structure]] which stores elements (variables) aligned in a computer's memory. Arrays are referenced by an [[identifier]] (variable name) and an index specifying a desired element.

	The array concept seems complex but the concept can be easily grasped. Why are arrays so important? The array is a fundamental data structure ~~which is often~~ found in ~~a vast amount of programs~~.		The array concept seems complex but the concept can be easily grasped. Why are arrays so important? The array is a fundamental data structure found in most programming languages.

	This tutorial targets people who are beginners. To understand how arrays work, it is imperative to try out and modify the provided samples. Make sure that each concept is understood before the next concept is attempted. This tutorial assumes the use of the SciTE editor. There is a minimal version of SciTE included in the latest stable release of AutoIt (version 3.2.0.1 and above).		This tutorial targets people who are beginners. To understand how arrays work, it is imperative to try out and modify the provided samples. Make sure that each concept is understood before the next concept is attempted. This tutorial assumes the use of the SciTE editor. There is a minimal version of SciTE included in the latest stable release of AutoIt (version 3.2.0.1 and above).

Mlipok: /* More Information */ UDF links

2014-06-17T18:48:41Z

More Information: UDF links

← Older revision		Revision as of 18:48, 17 June 2014
Line 386:		Line 386:
	== More Information ==		== More Information ==

	AutoIt features a large list of [[User Defined Functions~~\|User-Defined Functions]~~ (UDF), among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions Reference].		AutoIt features a large list of [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions (UDF)], among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions Reference].

	[[Category:Tutorials]]		[[Category:Tutorials]]

Mlipok: added a few links to online documentation

2014-06-16T18:40:34Z

added a few links to online documentation

← Older revision		Revision as of 18:40, 16 June 2014
Line 101:		Line 101:
	</syntaxhighlight>		</syntaxhighlight>

	When you run the above code you will see that $iMax is four and not three as you might have expected. The reason for this is that the developer of the StringSplit() function thought it was a good idea to use the first item (item zero) to keep a count of valid items in the array. This makes sense in many situations as you now have an array containing data with an index starting at one. So our sample code can now be rewritten like this.		When you run the above code you will see that $iMax is four and not three as you might have expected. The reason for this is that the developer of the {{Help File\|StringSplit}} function thought it was a good idea to use the first item (item zero) to keep a count of valid items in the array. This makes sense in many situations as you now have an array containing data with an index starting at one. So our sample code can now be rewritten like this.

	<syntaxhighlight lang='autoit'>		<syntaxhighlight lang='autoit'>
Line 120:		Line 120:
	There is another good reason for keeping the count in $arr[0]. When you start to use arrays extensively, you will encounter situations where you have to create an array without knowing how many of the elements you will use. Resizing the array is a relatively expensive operation (in CPU cycles) in most languages.		There is another good reason for keeping the count in $arr[0]. When you start to use arrays extensively, you will encounter situations where you have to create an array without knowing how many of the elements you will use. Resizing the array is a relatively expensive operation (in CPU cycles) in most languages.

	Now consider our example if our initial array has reserved space for ten items but we end up only using three. In this case iterating the array using UBound will force us to check for empty elements. While iterating with $arr[0] needs no other change than maintaining the correct count in $arr[0].		Now consider our example if our initial array has reserved space for ten items but we end up only using three. In this case iterating the array using {{Help File\|UBound}} will force us to check for empty elements. While iterating with $arr[0] needs no other change than maintaining the correct count in $arr[0].

	<syntaxhighlight lang='autoit'>		<syntaxhighlight lang='autoit'>
Line 137:		Line 137:
	== Changing Array Sizes With ReDim ==		== Changing Array Sizes With ReDim ==

	As arrays are critical to algorithm implementations, and in AutoIt even more so as there is no other means of grouping data, we have to understand how to let it grow and shrink. This is where the keyword ReDim comes into the picture.		As arrays are critical to algorithm implementations, and in AutoIt even more so as there is no other means of grouping data, we have to understand how to let it grow and shrink. This is where the keyword {{Help File\|ReDim}} comes into the picture.

	Let's make an example. We want our array to hold data lines but we don't know how many items we need. We make a guess, in this case five. Now, we use that array to hold data we get from a loop with a random number of iterations. If the array is too small it should automatically be increased. Before we dump the array to output, we should adjust it to the exact size it is supposed to be.		Let's make an example. We want our array to hold data lines but we don't know how many items we need. We make a guess, in this case five. Now, we use that array to hold data we get from a loop with a random number of iterations. If the array is too small it should automatically be increased. Before we dump the array to output, we should adjust it to the exact size it is supposed to be.
Line 179:		Line 179:
	== Passing Arrays to Functions ==		== Passing Arrays to Functions ==

	There is no special syntax required to pass an array as a function argument unlike a low level language such as C. The following example demonstrates:		There is no special syntax required to pass an array as a function argument unlike a low level language such as C.
			The following example demonstrates:

	<syntaxhighlight lang="AutoIt">		<syntaxhighlight lang="AutoIt">
Line 195:		Line 196:
	</syntaxhighlight>		</syntaxhighlight>

	You can not declare the variable to hold the array in the function declaration as an array. So, users could pass on a variable. So you have to check that the variable holds an array before you do array specific operations on it. The following code example will cause an error:		You can not declare the variable to hold the array in the function declaration as an array. So, users could pass on a variable. So you have to check that the variable holds an array before you do array specific operations on it.
			The following code example will cause an error:

	<syntaxhighlight lang="AutoIt">		<syntaxhighlight lang="AutoIt">
Line 384:		Line 386:
	== More Information ==		== More Information ==

	AutoIt features a large list of [[User Defined Functions\|User-Defined Functions] (UDF), among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named 'User Defined Functions Reference'.		AutoIt features a large list of [[User Defined Functions\|User-Defined Functions] (UDF), among which is a module supplying extra array functions. You can find a reference on those functions in AutoIt's Help file as the last main chapter named [http://www.autoitscript.com/autoit3/docs/libfunctions.htm User Defined Functions Reference].

	[[Category:Tutorials]]		[[Category:Tutorials]]