User:SuzannaLinn Resident/LuaLanguage1 - Revision history

SuzannaLinn Resident at 15:33, 23 April 2025

2025-04-23T15:33:21Z

← Older revision		Revision as of 08:33, 23 April 2025
Line 536:		Line 536:
	info = sayInfo,		info = sayInfo,
	give = giveObject,		give = giveObject,
	link = ~~giftLink~~,		link = giveLink,
	agent = sayAgentProfileLink,		agent = sayAgentProfileLink,
	group = sayGroupProfileLink		group = sayGroupProfileLink

SuzannaLinn Resident at 10:31, 4 October 2024

2024-10-04T10:31:22Z

← Older revision		Revision as of 03:31, 4 October 2024
Line 598:		Line 598:

	In lines 22-28 we create the table, with the name of the option as the key, and the function (without parentheses) as the value.		In lines 22-28 we create the table, with the name of the option as the key, and the function (without parentheses) as the value.

			"local", in line 22, means that the table is a local variable of the function, without "local" it would be a global variable.

	In line 30 we check if the option exists and we call the function, adding the parentheses.		In line 30 we check if the option exists and we call the function, adding the parentheses.

SuzannaLinn Resident at 10:25, 3 October 2024

2024-10-03T10:25:30Z

← Older revision		Revision as of 03:25, 3 October 2024
Line 437:		Line 437:
	-- Apple: 50		-- Apple: 50
	end		end


	fruitQuantity[ "Lemon" ] = 2		fruitQuantity[ "Lemon" ] = 2
Line 444:		Line 445:

	fruitQuantity[ "Lemon" ] = nil		fruitQuantity[ "Lemon" ] = nil
			-- Apple, Banana, Melon, Orange


			fruitQuantity.Pear = 1
			-- Apple, Banana, Melon, Orange, Pear

			print( fruitQuantity.Pear ) -- 1

			fruitQuantity.Pear = nil
	-- Apple, Banana, Melon, Orange		-- Apple, Banana, Melon, Orange
	</syntaxhighlight>		</syntaxhighlight>
Line 464:		Line 474:
	// Orange: 15		// Orange: 15
	}		}


	llLinksetDataWrite( "Lemon", "2" );		llLinksetDataWrite( "Lemon", "2" );
Line 472:		Line 483:
	llLinksetDataDelete( "Lemon" );		llLinksetDataDelete( "Lemon" );
	// Apple, Banana, Melon, Orange		// Apple, Banana, Melon, Orange








			//
	</syntaxhighlight>		</syntaxhighlight>
	\|}		\|}
Line 483:		Line 503:

	We read and write values in the array using [ and ] with the key. We delete a key-value by assigning the key to nil.		We read and write values in the array using [ and ] with the key. We delete a key-value by assigning the key to nil.

			And alternative way is with tablename.key, lines 28-34.

SuzannaLinn Resident at 10:16, 3 October 2024

2024-10-03T10:16:52Z

← Older revision		Revision as of 03:16, 3 October 2024
Line 466:		Line 466:

	llLinksetDataWrite( "Lemon", "2" );		llLinksetDataWrite( "Lemon", "2" );
	-- Apple, Banana, Melon, Orange, Lemon		// Apple, Banana, Melon, Orange, Lemon

	llSay( 0, llLinksetDataRead( "Lemon" ) ); // 2		llSay( 0, llLinksetDataRead( "Lemon" ) ); // 2

	llLinksetDataDelete( "Lemon" );		llLinksetDataDelete( "Lemon" );
	-- Apple, Banana, Melon, Orange		// Apple, Banana, Melon, Orange
	</syntaxhighlight>		</syntaxhighlight>
	\|}		\|}

SuzannaLinn Resident at 10:15, 3 October 2024

2024-10-03T10:15:54Z

@@ Line 437: / Line 437: @@
      -- Apple: 50
 end
 </syntaxhighlight>
+|
@@ Line 456: / Line 464: @@
      // Orange: 15
+}
 </syntaxhighlight>
 |}
@@ Line 465: / Line 481: @@
 We see that the fruits are printed in a random order. This happens because tables are implemented as hash tables. It is more efficient, but it results in an undefined order when iterating over the elements. We will see later how to sort them.

SuzannaLinn Resident at 10:05, 3 October 2024

2024-10-03T10:05:08Z

← Older revision		Revision as of 03:05, 3 October 2024
Line 385:		Line 385:
	The tables are the most important data structure in Lua.		The tables are the most important data structure in Lua.

	~~In the viewer~~ we ~~see~~ an example of a table used as an array, in the same way as LSL lists.		Here we have an example of a table used as an array, in the same way as LSL lists.

	{ and } are used instead of [ and ] to initialize it.		{ and } are used instead of [ and ] to initialize it.
Line 393:		Line 393:
	"ipairs" is a system function that iterates on all the values of an array table. It returns two values, stored in "index" and "fruits". We will see in a while that functions can return several values.		"ipairs" is a system function that iterates on all the values of an array table. It returns two values, stored in "index" and "fruits". We will see in a while that functions can return several values.

	The arrays start from 1, not 0, as we can see in the results in lines 7-10. Also the first character in a string has the position 1 instead of 0.		The arrays start from 1, not 0, as we can see in the results in lines 7-10. Also the first character in a string has the position 1 instead of 0. All the Lua fuctions that work on array tables or string assume that they start at 1.

	The operator #, that we have seen previously returning the length of a string, also returns the number of elements in an array table.		The operator #, that we have seen previously returning the length of a string, also returns the number of elements in an array table.
Line 463:		Line 463:

	In the "for", line 10, we use "pairs" instead of "ipairs". "ipairs" is optimized for array tables and only works with them.		In the "for", line 10, we use "pairs" instead of "ipairs". "ipairs" is optimized for array tables and only works with them.

			We see that the fruits are printed in a random order. This happens because tables are implemented as hash tables. It is more efficient, but it results in an undefined order when iterating over the elements. We will see later how to sort them.

SuzannaLinn Resident at 09:50, 3 October 2024

2024-10-03T09:50:36Z

← Older revision		Revision as of 02:50, 3 October 2024
Line 316:		Line 316:
	\|}		\|}
	This is how LL functions will look in LuaSL. We will have all the LL functions (including LinksetData, Experiences, all) with the same parameters and constants and the difference will be calling them with a "." between "ll" and the name of the function.		This is how LL functions will look in LuaSL. We will have all the LL functions (including LinksetData, Experiences, all) with the same parameters and constants and the difference will be calling them with a "." between "ll" and the name of the function.


	== Tables as lists ==		== Tables as lists ==

SuzannaLinn Resident: /* Functions, ll functions */

2024-10-03T09:49:46Z

Functions, ll functions

← Older revision		Revision as of 02:49, 3 October 2024
Line 294:		Line 294:
	The functions use the keyword "function" and, of course, no types for the parameters or the return value.		The functions use the keyword "function" and, of course, no types for the parameters or the return value.

	~~In the viewer~~ we ~~see~~ two example functions, lines 2-7 and lines 10-27.		Here we have two example functions, lines 2-7 and lines 10-27.

	In line 12 we return "nil" instead of "-1". The value "nil" means that the variable has no value, it's empty. We use it again in line 23.		In line 12 we return "nil" instead of "-1". The value "nil" means that the variable has no value, it's empty. We use it again in line 23.
Line 316:		Line 316:
	\|}		\|}
	This is how LL functions will look in LuaSL. We will have all the LL functions (including LinksetData, Experiences, all) with the same parameters and constants and the difference will be calling them with a "." between "ll" and the name of the function.		This is how LL functions will look in LuaSL. We will have all the LL functions (including LinksetData, Experiences, all) with the same parameters and constants and the difference will be calling them with a "." between "ll" and the name of the function.


	== Tables as lists ==		== Tables as lists ==

SuzannaLinn Resident at 09:48, 3 October 2024

2024-10-03T09:48:24Z

← Older revision		Revision as of 02:48, 3 October 2024
Line 3:		Line 3:
	I'm using "Luau" at the end of the comment in the first line for Luau only code.		I'm using "Luau" at the end of the comment in the first line for Luau only code.
	I'm using "LuaSL" for presumed LuaSL only code.		I'm using "LuaSL" for presumed LuaSL only code.


	== Types and variables ==		== Types and variables ==
Line 83:		Line 84:

	- Linting identifies possible issues like uninitialized or unused variables, duplicated functions, mismatched parameter counts, return values, and many more. There are also directives to enable or disable specific linting checks.		- Linting identifies possible issues like uninitialized or unused variables, duplicated functions, mismatched parameter counts, return values, and many more. There are also directives to enable or disable specific linting checks.


	== Operators ==		== Operators ==
Line 154:		Line 156:

	The compound operators, += and so on, doesn't exist in standard Lua, but they exist in Luau, so LuaSL will also have them: +=, -=, *=, /=, //=, %=, ^=.		The compound operators, += and so on, doesn't exist in standard Lua, but they exist in Luau, so LuaSL will also have them: +=, -=, *=, /=, //=, %=, ^=.


	== If, while, for, repeat ==		== If, while, for, repeat ==
Line 225:		Line 228:

	We can't use an assignment in a condition. In Lua, assignments are statements, not expressions. In case that we write a = instead of a == in a condition, we will get an error when compiling.		We can't use an assignment in a condition. In Lua, assignments are statements, not expressions. In case that we write a = instead of a == in a condition, we will get an error when compiling.


	== Functions, ll functions ==		== Functions, ll functions ==

SuzannaLinn Resident: /* If, while, for, repeat */

2024-10-03T09:47:08Z

If, while, for, repeat

← Older revision		Revision as of 02:47, 3 October 2024
Line 220:		Line 220:
	There are the same blocks if, while and for. And a repeat..until instead of do...while ("repeat..until not" is the same as "do...while").		There are the same blocks if, while and for. And a repeat..until instead of do...while ("repeat..until not" is the same as "do...while").

	The { and } are not used here (they are used for tables as we will see later). Instead there are keywords, "then" or "do", and "end".		The { and } are not used here (they are used for tables as we will see later). Instead there are keywords: "then" or "do", and "end".

	The "for" in lines 20-22 is one of the types of "for", we will see the other one later. Its 3 values are start, end and step.		The "for" in lines 20-22 is one of the types of "for", we will see the other one later. Its three values are start, end and step.

	~~We can't use an assignment in a condition. In Lua assignments are statements, not expressions.~~

	~~In case that we write a = instead of a == in a condition, we will get an error when compiling~~.

			We can't use an assignment in a condition. In Lua, assignments are statements, not expressions. In case that we write a = instead of a == in a condition, we will get an error when compiling.

	== Functions, ll functions ==		== Functions, ll functions ==