How to optimize code and when not to.

On it's own probably not. But the cumulative effect of these optimisations can be significant for some types of scripts. My racing system for example. The more memory I save, the higher the number of lap times that can be recorded per race is. Of course there, finding the right performance / memory balance is important. So as the ones you quoted are slower, I won't be using those this time, but many of the others in this thread do get liberal use in the code

OK, so all the talk about optimization is sweet, but leaves several questions:

1) what is the compiled scipt byte code limit?
2) Where do you find how much your your code is consuming?
3) Is the code memory limit 16K for a script?
4) How do you tell how much memory is being used?
5) What kinds of Compile errors do you see when you exceed the compliled byte code limit.
6) What kinds of errors do you see when you get a memory overflow?
7) Is there one place where this is actually explained for the young uns?

Val (fairly experienced scripter who is just now beginning to encounter these problems)

That's what people say - LSL uses less memory if you don't make it do int->float conversions. That is, it's cheaper to say 0.0 than it is to use 0 when a float is required.

Personally, I consider that a compiler bug but it's better form to use the correct notation so it's not an annoying bug.


I'd be surprised if there was a difference. That's more of a parsing thing than a code generation thing.

1+3) You get 16kb for code+stack+heap
2+4) llGetFreeMemory()
5) Byte code assembly failed -- out of memory
6) Stack/heap collision. You have to be there when it happens to see the error. The script will be stopped but I think the running box will still be a checked. You have to use another script that checks its state to see that it crashed.
7) The (old) wiki

no

Whatever this thread did to my brain, *wonders about this fuzzy feeling*
but I feel much more enlighted about the inner workings of programming languages

Thanks