Talk:LSL Language Test - Revision history

Strife Onizuka: New section: Size

2008-02-06T22:37:19Z

New section: Size

← Older revision		Revision as of 15:37, 6 February 2008
Line 33:		Line 33:

	It is definitely an error in the LSO compiler. It should return 1.0, it should NOT return 0.0. What it currently returns is not infact 0.0 but 0x1p-149 (use [[Float2Hex]] to show this). What is happening is that an integer is being pushed into a stack position that later gets read back out as a float. This is most definitely a compiler error, integer to float conversion has an implicit typecast but it seems that the compiler forgot to make it explicit. It would be nice to have some LSL function that does two way conversions from floats to integers and back based on how they are stored in memory. -- [[User:Strife Onizuka\|Strife Onizuka]] 11:30, 5 February 2008 (PST)		It is definitely an error in the LSO compiler. It should return 1.0, it should NOT return 0.0. What it currently returns is not infact 0.0 but 0x1p-149 (use [[Float2Hex]] to show this). What is happening is that an integer is being pushed into a stack position that later gets read back out as a float. This is most definitely a compiler error, integer to float conversion has an implicit typecast but it seems that the compiler forgot to make it explicit. It would be nice to have some LSL function that does two way conversions from floats to integers and back based on how they are stored in memory. -- [[User:Strife Onizuka\|Strife Onizuka]] 11:30, 5 February 2008 (PST)

			== Size ==

			I've got a problem, I was about to release a new version of the script... but it's too big to compile in LSO. It's all the function calls, they eat up the memory and stack. -- [[User:Strife Onizuka\|Strife Onizuka]] 14:37, 6 February 2008 (PST)

Strife Onizuka: /* LSO failure */

2008-02-05T19:54:54Z

LSO failure

← Older revision		Revision as of 12:54, 5 February 2008
Line 32:		Line 32:
	-- {{User\|Scouse Linden}} 21:53, 5 February 2008		-- {{User\|Scouse Linden}} 21:53, 5 February 2008

	It is definitely an error in LSO. It should return 1.0, it should NOT return 0.0. What it currently returns is not infact 0.0 but 0x1p-149 (use [[Float2Hex]] to show this). What is happening is that an integer is being pushed into a stack position that later gets read back out as a float. This is most definitely a compiler error, integer to float conversion has an implicit typecast but it seems that the compiler forgot to make it explicit. It would be nice to have some LSL function that does two way conversions from floats to integers and back based on how they are stored in memory. -- [[User:Strife Onizuka\|Strife Onizuka]] 11:30, 5 February 2008 (PST)		It is definitely an error in the LSO compiler. It should return 1.0, it should NOT return 0.0. What it currently returns is not infact 0.0 but 0x1p-149 (use [[Float2Hex]] to show this). What is happening is that an integer is being pushed into a stack position that later gets read back out as a float. This is most definitely a compiler error, integer to float conversion has an implicit typecast but it seems that the compiler forgot to make it explicit. It would be nice to have some LSL function that does two way conversions from floats to integers and back based on how they are stored in memory. -- [[User:Strife Onizuka\|Strife Onizuka]] 11:30, 5 February 2008 (PST)

Strife Onizuka at 19:30, 5 February 2008

2008-02-05T19:30:36Z

← Older revision		Revision as of 12:30, 5 February 2008
Line 30:		Line 30:
	</lsl>		</lsl>
	Do you think it should be 0.0 or 1.0? We may fix this LSL2 bug once we have fewer Mono bugs to fix.		Do you think it should be 0.0 or 1.0? We may fix this LSL2 bug once we have fewer Mono bugs to fix.
			-- {{User\|Scouse Linden}} 21:53, 5 February 2008

			It is definitely an error in LSO. It should return 1.0, it should NOT return 0.0. What it currently returns is not infact 0.0 but 0x1p-149 (use [[Float2Hex]] to show this). What is happening is that an integer is being pushed into a stack position that later gets read back out as a float. This is most definitely a compiler error, integer to float conversion has an implicit typecast but it seems that the compiler forgot to make it explicit. It would be nice to have some LSL function that does two way conversions from floats to integers and back based on how they are stored in memory. -- [[User:Strife Onizuka\|Strife Onizuka]] 11:30, 5 February 2008 (PST)

Scouse Linden: /* LSO failure */

2008-02-05T16:53:35Z

LSO failure

← Older revision		Revision as of 09:53, 5 February 2008
Line 21:		Line 21:
	FAILED: testReturnFloat() (0.000000 expected 1.000000)		FAILED: testReturnFloat() (0.000000 expected 1.000000)
	It only happens if you try returning an int as a float - returning a float as a float works as expected. I can't test behaviour under mono because there isn't a TG beta grid. - [[User:Katharine Berry\|Katharine Berry]] 11:08, 4 February 2008 (PST)		It only happens if you try returning an int as a float - returning a float as a float works as expected. I can't test behaviour under mono because there isn't a TG beta grid. - [[User:Katharine Berry\|Katharine Berry]] 11:08, 4 February 2008 (PST)

			Yes, look at the test.
			<lsl>
			float testReturnFloat()
			{
			return 1;
			}
			</lsl>
			Do you think it should be 0.0 or 1.0? We may fix this LSL2 bug once we have fewer Mono bugs to fix.

Katharine Berry: New section: LSO failure

2008-02-04T19:08:40Z

New section: LSO failure

← Older revision		Revision as of 12:08, 4 February 2008
Line 15:		Line 15:
	ensureIntegerEqual("i = 2; (i == 1) && (--i == 1)", (i == 1) && (--i == 1), TRUE);</lsl>		ensureIntegerEqual("i = 2; (i == 1) && (--i == 1)", (i == 1) && (--i == 1), TRUE);</lsl>
	These tests are good for LSO-LSL but do we want to propagate this order of execution to Mono-LSL? -- [[User:Strife Onizuka\|Strife Onizuka]] 19:16, 7 December 2007 (PST)		These tests are good for LSO-LSL but do we want to propagate this order of execution to Mono-LSL? -- [[User:Strife Onizuka\|Strife Onizuka]] 19:16, 7 December 2007 (PST)

			== LSO failure ==

			Is this expected under the existing system?
			FAILED: testReturnFloat() (0.000000 expected 1.000000)
			It only happens if you try returning an int as a float - returning a float as a float works as expected. I can't test behaviour under mono because there isn't a TG beta grid. - [[User:Katharine Berry\|Katharine Berry]] 11:08, 4 February 2008 (PST)

Strife Onizuka: New page: // post increment. i = 1; ensureIntegerEqual("i = 1; (i == 2) && (i++ == 1)", (i == 2) && (i++ == 1), TRUE); // pre increment. i = 1; ensureIntegerEqu...

2007-12-08T03:16:04Z

New page: <lsl> // post increment. i = 1; ensureIntegerEqual("i = 1; (i == 2) && (i++ == 1)", (i == 2) && (i++ == 1), TRUE); // pre increment. i = 1; ensureIntegerEqu...

New page

<lsl> // post increment.
i = 1;
ensureIntegerEqual("i = 1; (i == 2) && (i++ == 1)", (i == 2) && (i++ == 1), TRUE);

// pre increment.
i = 1;
ensureIntegerEqual("i = 1; (i == 2) && (++i == 2)", (i == 2) && (++i == 2), TRUE);

// post decrement.
i = 2;
ensureIntegerEqual("i = 2; (i == 1) && (i-- == 2)", (i == 1) && (i-- == 2), TRUE);

// pre decrement.
i = 2;
ensureIntegerEqual("i = 2; (i == 1) && (--i == 1)", (i == 1) && (--i == 1), TRUE);</lsl>
These tests are good for LSO-LSL but do we want to propagate this order of execution to Mono-LSL? -- [[User:Strife Onizuka|Strife Onizuka]] 19:16, 7 December 2007 (PST)