Missing something obvious...

Ok, so I'm new to LSL and thought I'd try something simple stupid... which has now backfired spectacularly. Could someone please tell me what the blazes is wrong with the following?:

default
{
touch_start(integer total_number)
{
float g = 0;
g = 220/256;
llSay( DEBUG_CHANNEL, "g has a value of: " + (string)g );
}
}

It keeps on saying that g is 0.000 when it should be 0.86???

Thanks in advance!

You stated g = 0, and then in the same event stated g = 220/250.

When declaring a variable, you can just put something like


Without any initial value for 'g'. Otherwise you're contradicting yourself, and saying it has two values.

Thanks for the reply but I'm now even more confused- if that's the case, then how am I supposed to actually do any operations on the variable? E.g. Say g starts off as 1.2 and I want to change it later in the same touch state to another value.

PS: I just tried doing it your way and I'm still getting the same thing

Not declaring g as 0 won't make any difference to the output, as g's value will be re-assigned in the next line.

However this code works....

default
{
	touch_start(integer total_number)
	{
		float g;
		g = 220.0 / 256.0;
		llSay(0, "g has a value of: " + (string)g);
	}
}

Added the .0 to the end of the numbers

I thought that was the case, but it was all I could think of.

Upon thinking on it, was the problem caused by it being a float, and the equation using integers?

Without the .0, they might be seen only as integers to the system, I mean, I'm not sure.

(Ive never thought about it before)

Oh for crying out loud... knew it had to be something obvious! Thanks a million for the help Borat & Keira- much appreciated!

I believe so yes, once I had added the .0 on the end they were recognized as being floats, another way of doing it (although obviously klunky) is to cast the integers to floats like (float)220 / (float)250

YW Amael

When you do the integer divide 220/256, you are i believe implicitly coercing g to be an integer, even if you had declared it as:

float g=0.0;

which would be a safer declaration. LSL is picky that way.
.