YENGconstant - Revision history

Djphil: Line number clarification

2021-03-16T22:04:49Z

Line number clarification

2020-11-20T22:36:07Z

2020-11-20T22:35:34Z

2020-09-22T12:36:23Z

Add into category

2020-09-20T06:39:29Z

2020-09-20T06:38:30Z

2020-09-20T06:37:50Z

2020-09-20T06:34:19Z

2020-09-20T06:27:16Z

2020-09-20T06:26:42Z

@@ Line 1: / Line 1: @@
 constant allows to define a constant value that is evaluated and all its occurrences in code are replaced by that value at compile time.
-  Make sure to include yoptions; on second line of script.
+  Make sure to add yoptions; to the second line of the script, usually line number 1 starting from 0.
 Its type will be guessed from the types at right side expression, and can be confusing

@@ Line 15: / Line 15: @@
   & | ^ ~ for integer types
   - * / % for integer or float types
-−
 On expressions better use () to force and make clear the desired evaluation order
   constant ar = 2 + (2 & 1); //will be 2

@@ Line 1: / Line 1: @@
-constant allows to define a constant value that is evaluated and all its occurrences in code are replaced by that value at compile time.<br>
+constant allows to define a constant value that is evaluated and all its occurrences in code are replaced by that value at compile time.
-its type will be guessed from the types at right side expression, and can be confusing
   constant endlimit = 0.1 // will be a like float 0.1
@@ Line 9: / Line 12: @@
   constant badidea = "2" + 3 // will be like string "23"
-other operations supported
+Other operations supported
   & | ^ ~ for integer types
   - * / % for integer or float types
-on expressions better use () to force and make clear the desired evaluation order
+On expressions better use () to force and make clear the desired evaluation order
   constant ar = 2 + (2 & 1); //will be 2
   constant ar = 2 + 2 & 1; //will be 0, ie will do (2 + 2) & 1 since + and & have same evaluation priority.
-simple normal use will be to define a simple constant at top of program, easy to change later.
+Simple normal use will be to define a simple constant at top of program, easy to change later.
   constant textureID = "0d3b69fe-1b6e-40f3-8e5f-933814df3b7b";

← Older revision		Revision as of 12:36, 22 September 2020
Line 21:		Line 21:
	constant textureID = "0d3b69fe-1b6e-40f3-8e5f-933814df3b7b";		constant textureID = "0d3b69fe-1b6e-40f3-8e5f-933814df3b7b";

−	~~saving~~ the memory of a global variable	+	Saving the memory of a global variable.
		+
		+	[[Category:Scripts]]

← Older revision		Revision as of 06:39, 20 September 2020
Line 20:		Line 20:

	constant textureID = "0d3b69fe-1b6e-40f3-8e5f-933814df3b7b";		constant textureID = "0d3b69fe-1b6e-40f3-8e5f-933814df3b7b";
		+
		+	saving the memory of a global variable

@@ Line 2: / Line 2: @@
 its type is by the types are right side expression, and very confusing
-  constant endlimit = 0.1 // will be a float
+  constant endlimit = 0.1 // will be a like float 0.1
-  constant start = 1 // will be a integer
+  constant start = 1 // will be a like integer 1
-  constant idea = 2 + 3 // will be integer 5
+  constant idea = 2 + 3 // will be like integer 5
-  constant idea = 2 + 3.0 // will be string 5.0 since it is at compile time will mean integer 5
+  constant betteridea = idea + 3 // will be like integer 8
-  constant badidea = "2" + 3 // will be string "23"
+ constant otheridea = 2 + 3.0 // will be like float 5.0
 This last example illustrates that mixed types, specially when one is a string, can be confusing, and should be avoid<br>
@@ Line 14: / Line 15: @@
   - * / % for integer or float types
-note that evaluation order is not the best, the use of () is a must
+on expressions better use () to force and make clear the desired evaluation order
   constant ar = 2 + (2 & 1); //will be 2
-  constant ar = 2 + 2 & 1; //will be 0, ie code did (2 + 2) & 1
+  constant ar = 2 + 2 & 1; //will be 0, ie will do (2 + 2) & 1 since + and & have same evaluation priority.
 possible the use of any operation should just be avoid.<br>