Difference between revisions of "LSL Constants vs Globals"
Jump to navigation
Jump to search
(→Cons) |
|||
Line 6: | Line 6: | ||
===Cons=== | ===Cons=== | ||
* Uses more bytecode when it is shorter then 3 characters or it used once. | * Uses more bytecode when it is shorter then 3 characters or it used once. | ||
{| {{Prettytable|style=margin-top:0;}} | {| {{Prettytable|style=margin-top:0;}} | ||
|+ Figure | |+ Figure 1: Bytecode Cost | ||
|- {{Hl2}} | |- {{Hl2}} | ||
! Constant | ! Constant |
Revision as of 08:20, 8 July 2008
There are some advantages in using global variables over the string and key constants, it's faster and uses less bytecode when it is longer then 3 characters and it used more then twice but it uses more bytecode when it is shorter then 3 characters or it used once. This is easily demonstrated by running the scripts in Figure 2.
Pros
- Faster
- Uses less bytecode when it is longer then 3 characters and it used more then twice.
Cons
- Uses more bytecode when it is shorter then 3 characters or it used once.
Constant | Global |
---|---|
<lsl> dead(){ key a = NULL_KEY; key b = NULL_KEY; key c = NULL_KEY; key d = NULL_KEY; } default { state_entry() { llOwnerSay(llGetFreeMemory()); } }</lsl> |
<lsl>key null_key = NULL_KEY; dead(){ key a = null_key; key b = null_key; key c = null_key; key d = null_key; } default { state_entry() { llOwnerSay(llGetFreeMemory()); } }</lsl> |