Difference between revisions of "Array Reference"
imported>Egocarib (added new warning about problem with array.find()) |
imported>Evildavo m (Noted the restriction that arrays can only be between 1 and 128 in the Array Creation section.) |
||
Line 20: | Line 20: | ||
<array creation> ::= 'new' <element type> '[' <int> ']' | <array creation> ::= 'new' <element type> '[' <int> ']' | ||
To create an array, use the "new" keyword, followed by the type and size. The Size is denoted by the integer between the two square brackets, and cannot be a variable. (In other words, array size must be defined at compile time) | To create an array, use the "new" keyword, followed by the type and size. The Size is denoted by the integer between the two square brackets, which must be between 1 and 128. Also, it cannot be a variable. (In other words, array size must be defined at compile time) | ||
The initial value of each element will be the [[Default Value Reference|default value]] for the type. | The initial value of each element will be the [[Default Value Reference|default value]] for the type. | ||
Line 74: | Line 74: | ||
<br> | <br> | ||
== Warnings == | == Warnings == | ||
*Only the = operator can be used with an [[Arrays_(Papyrus)|array]] (see [[Operator_Reference#Assignment_Operators|Assignment Operators]]): | *Only the = assignment operator can be used with an [[Arrays_(Papyrus)|array]] (see [[Operator_Reference#Assignment_Operators|Assignment Operators]]): | ||
<source lang="papyrus"> | <source lang="papyrus"> | ||
; Will not compile, as the compiler doesn't know how to handle it. | ; Will not compile, as the compiler doesn't know how to handle it. | ||
Line 80: | Line 80: | ||
</source> | </source> | ||
<br> | <br> | ||
*The array Find() function | === Compiler Issues === | ||
Several compiler errors have been identified that are caused by using expressions inside of array index brackets. The standard papyrus compiler sometimes compiles expressions inside of array index brackets incorrectly, leading to unexpected behavior and data corruption. As a result, it is recommended to avoid using complex expressions or function calls inside of array index brackets when possible. '''[http://forums.bethsoft.com/topic/1491368-weird-array-index-behavior/ See this discussion]''' for further details and analysis of the problems outlined below: | |||
<br> | |||
*Using complex expressions inside of the index brackets of an integer array can cause unexpected behavior - | |||
<source lang="papyrus"> | |||
;these work fine: | |||
myIntArray[i] = newValue | |||
myIntArray[i * 5] = newValue | |||
;this will result in unexpected values being inserted into the array at run time: | |||
myIntArray[i * 5 + 1] = newValue | |||
</source> | |||
<br> | |||
*The array Find() function should not be used within an array's index brackets; it can also cause unexpected results - | |||
<source lang="papyrus"> | <source lang="papyrus"> | ||
;this works fine: | ;this works fine: | ||
Line 86: | Line 100: | ||
myArray[i] = newValue ;(and fill it with our newValue) | myArray[i] = newValue ;(and fill it with our newValue) | ||
;this will | ;this will result in values being inserted into unpredictable indices of the array at run time: | ||
myArray[myArray.Find(none)] = newValue | myArray[myArray.Find(none)] = newValue | ||
</source> | </source> |
Revision as of 08:45, 13 December 2014
Arrays are values that contain several other values, indexed by a 0-based number. (0 is the first element, 1 in the second, and so on).
Array Type
<array type> ::= <element type> '[' ']'
An array type is denoted by adding a pair of empty brackets after the type of the elements. The element type may only be a non-array type, so multi-dimentional arrays are not allowed. These types can be used anywhere else other types are used - as parameter, return, variable, and property types.
Examples
; An array of integers
int[]
; An array of MyObjects
MyObject[]
Array Creation
<array creation> ::= 'new' <element type> '[' <int> ']'
To create an array, use the "new" keyword, followed by the type and size. The Size is denoted by the integer between the two square brackets, which must be between 1 and 128. Also, it cannot be a variable. (In other words, array size must be defined at compile time)
The initial value of each element will be the default value for the type.
If you make an array property, then the Creation Kit will determine the size of the array by how many elements are put into it.
Note that this cannot appear in the script outside of a function.
Examples
; Create an array of 20 floats
float[] x = new float[20]
; Create an array of 5 MyScripts
MyScript[] x = new MyScript[5]
Array Length
<array length> ::= <expression> '.' 'Length'
To get the length of an array, you can access the read-only length property on the variable holding the array. If the variable is None, the length will still succeed, but return 0. Note that the last valid index in an array is the length of the array, minus 1.
Examples
; Get the length of our array
int[] myArray = new int[10]
x = myArray.Length ; x will get 10
; Get the length of an uninitialized array (None)
float[] myArray
x = myArray.Length ; x will get 0
Array Elements
<array access> ::= <expression> '[' <expression> ']'
To get a specific array element, just put the index of the element you want between two square brackets. This value can also come from an expression, or a return value of a function, or something else (see Warnings below for an exception). The valid elements in an array are from 0 to the length minus 1.
Examples
; get the first element in the array
x = myArray[0]
; get the last element of the array
x = myArray[myArray.Length - 1]
Warnings
- Only the = assignment operator can be used with an array (see Assignment Operators):
; Will not compile, as the compiler doesn't know how to handle it.
myArray[3] += 5
Compiler Issues
Several compiler errors have been identified that are caused by using expressions inside of array index brackets. The standard papyrus compiler sometimes compiles expressions inside of array index brackets incorrectly, leading to unexpected behavior and data corruption. As a result, it is recommended to avoid using complex expressions or function calls inside of array index brackets when possible. See this discussion for further details and analysis of the problems outlined below:
- Using complex expressions inside of the index brackets of an integer array can cause unexpected behavior -
;these work fine:
myIntArray[i] = newValue
myIntArray[i * 5] = newValue
;this will result in unexpected values being inserted into the array at run time:
myIntArray[i * 5 + 1] = newValue
- The array Find() function should not be used within an array's index brackets; it can also cause unexpected results -
;this works fine:
i = myArray.Find(none) ;(find the first blank element)
myArray[i] = newValue ;(and fill it with our newValue)
;this will result in values being inserted into unpredictable indices of the array at run time:
myArray[myArray.Find(none)] = newValue