LSL Hacks

Template:Needs Translation/de Template:Needs Translation/es Template:Needs Translation/el Template:Needs Translation/fr Template:Needs Translation/he Template:Needs Translation/it Template:Needs Translation/ja Template:Needs Translation/ko Template:Needs Translation/nl Template:Needs Translation/hu Template:Needs Translation/no Template:Needs Translation/da Template:Needs Translation/sv Template:Needs Translation/tr Template:Needs Translation/pl Template:Needs Translation/pt Template:Needs Translation/ru Template:Needs Translation/th Template:Needs Translation/uk Template:Needs Translation/zh-Hans Template:Needs Translation/zh-Hant

A page dedicated LSL Hacks, those things that make your code so much better but at the same time so much worse.

llGetListLength(myList) and (myList != [])

Type: LSO

Discover: Strife Onizuka

• Instead of using llGetListLength(myList) you can use (myList != []).
• Instead of using -llGetListLength(myList) you can use ([] != myList).

Pros

• Faster
• Uses less bytecode

Cons

• Less readable
• Will likely be removed in LSL3^[1]

++c and c++

Type: LSO

Discover: Not Applicable

In LSO LSL (as opposed to Mono LSL) ++c is faster then c++ because of how the bytecode is generated^[2]. There are very few applications where ++c can't be used instead.

Pros

• Faster code.
• Saves 6 bytes and 2 instructions.

Cons

• None

(c = -~c) same as ++c

Type: LSO

Discover: Strife Onizuka

For the same instruction cost of (++c), (c = -~c) can be substituted giving a 4 byte saves.

Pros

• Saves 4 bytes of bytecode.

Cons

• Will fail on hardware that doesn't support two's compliment (unlikely LL will ever use such a platform).
• ?

Testing key validity

Type: LSO & Mono

Discover: Strife Onizuka

By passing the key value to a conditional, if it is valid and not a NULL_KEY then it will execute the true branch.

<lsl>integer isKey(key in) {

   if(in) return 2;
   return (in == NULL_KEY);

}</lsl>

Pros

• Fast
• Easy
• Painless

Cons

• None

Footnotes

1. ^ Plans for LSL3 are still being worked out, nothing has been finalized, no release date has been set, LSL3 may in-fact never happen.
2. ^ The LSO LSL compiler does not produce optimized code.