Difference between revisions of "NULL KEY"
m (lsl code tagging) |
m |
||
| Line 1: | Line 1: | ||
{{LSL Constant | {{LSL_Constant/string}}{{LSL Constant | ||
|name=NULL_KEY | |name=NULL_KEY | ||
|type=string | |type=string | ||
| Line 8: | Line 8: | ||
In most applications NULL_KEY isn't needed; an empty string will suffice. | In most applications NULL_KEY isn't needed; an empty string will suffice. | ||
|examples= | |examples= | ||
<lsl> | <lsl> | ||
Revision as of 16:21, 19 May 2008
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Description
Constant: string NULL_KEY = "00000000-0000-0000-0000-000000000000";The string constant NULL_KEY has the value "00000000-0000-0000-0000-000000000000"
While technically a string constant, it is only useful as a key.
Despite fitting the syntax criteria to be a valid key, when fed to a Conditional as a key it executes as false.
In most applications NULL_KEY isn't needed; an empty string will suffice.
Caveats
Related Articles
Functions
| • | llAvatarOnSitTarget | |||
| • | llDetectedKey | |||
| • | llGetNotecardLine | |||
| • | llGetLandOwnerAt | |||
| • | llGetPermissionsKey | |||
| • | llGetTexture | |||
| • | llListen |
Events
| • | attach |
Examples
<lsl> integer isKey(key in) {
if(in) return 2; return (in == NULL_KEY);
}//returns 2 if it's a valid key, 1 if it's NULL_KEY </lsl>
Notes
Like any LSO string constants longer then 3 characters and used in multiple places in the code, they should be stored in a global variable. The result will be a considerable memory savings. This does not apply to scripts compiled with Mono. See LSL Constants vs Globals for more information about this and examples.
test