Difference between revisions of "Category:LSL Types"
m (→Mutability) |
(example) |
||
| Line 9: | Line 9: | ||
<lsl>integer myVar = 123;</lsl> | <lsl>integer myVar = 123;</lsl> | ||
== | == Pass‑by‑value == | ||
[[LSL]] as a language uses | [[LSL]] as a language uses pass‑by‑value for all types{{Footnote|The VMs that run compiled scripts however do use reference types and pass‑by‑reference, they just ensure copies are made.}}. When a value (it can be the value in a variable) is passed as a parameter to a function, that function is provided with it's own unique copy of the value. So if in the course of executing the function, it modifies the parameter, that modification only changes the functions copy of the value, it does not effect or change the original (or other copies). | ||
*[[:Category:LSL Functions|Built in functions]] will never modify the variables used as parameters. | *[[:Category:LSL Functions|Built in functions]] will never modify the variables used as parameters. | ||
*User functions that change the values of parameters inside the function scope will not have those changes applied to the variables that supplied those parameters. | *User functions that change the values of parameters inside the function scope will not have those changes applied to the variables that supplied those parameters. | ||
===Example=== | |||
<lsl>//This demonstrates that LSL (as a language) is pass‑by‑value, if it were pass‑by‑reference, the lines said would be different. | |||
swap(string a, string b){ | |||
string t = a; | |||
a = b; | |||
b = t; | |||
} | |||
default { | |||
state_entry(){ | |||
string a = "1"; | |||
string b = "2"; | |||
llOwnerSay(llList2CSV([a, b])); | |||
swap(a, b);//fails to mutate a or b. | |||
llOwnerSay(llList2CSV([a, b])); | |||
} | |||
}</lsl> | |||
Revision as of 11:42, 27 April 2012
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Introduction
A data type is a definition of the type or format of data.
An integer for example, defines that the variable which will hold this kind (or 'type') of data shall contain only integers, which for 32-bit are whole number values in the range of 0x00000000 to 0xFFFFFFFF.
Example
<lsl>integer myVar = 123;</lsl>
Pass‑by‑value
LSL as a language uses pass‑by‑value for all types[1]. When a value (it can be the value in a variable) is passed as a parameter to a function, that function is provided with it's own unique copy of the value. So if in the course of executing the function, it modifies the parameter, that modification only changes the functions copy of the value, it does not effect or change the original (or other copies).
- Built in functions will never modify the variables used as parameters.
- User functions that change the values of parameters inside the function scope will not have those changes applied to the variables that supplied those parameters.
Example
<lsl>//This demonstrates that LSL (as a language) is pass‑by‑value, if it were pass‑by‑reference, the lines said would be different. swap(string a, string b){
string t = a; a = b; b = t;
}
default {
state_entry(){
string a = "1";
string b = "2";
llOwnerSay(llList2CSV([a, b]));
swap(a, b);//fails to mutate a or b.
llOwnerSay(llList2CSV([a, b]));
}
}</lsl>
Subcategories
This category has the following 8 subcategories, out of 8 total.