Difference between revisions of "Category:LSL String"

From Second Life Wiki
Jump to navigation Jump to search
(While writing such a function is interesting, it's not code that should ever be used. There is no value added by the code to justify the cost... and it doesn't work as advertised.)
(→‎Useful Functions: some of these are no longer useful)
 
(4 intermediate revisions by 4 users not shown)
Line 8: Line 8:
String values are enclosed in double quotes when defined in LSL text.
String values are enclosed in double quotes when defined in LSL text.


Any character may be used in a string though some will need to be escaped (see the [[#Escape Codes|Escape Codes section]] on this page for more info.)
Any character may be used in a string, except for the "NUL" character, though some will need to be escaped (see the [[#Escape Codes|Escape Codes section]] on this page for more info.) The "NUL" character is Unicode value U+0000 and cannot exist in an LSL string. Therefore for example llUnescapeURL("%00") results in an empty string "".


The length of a string is only limited by available [[LlGetFreeMemory|script memory]]. (see the [[#String_Length_Restraints|String Length Restraints]] section on this page for some operational restraints.)
The length of a string is only limited by available [[LlGetFreeMemory|script memory]]. (see the [[#String_Length_Restraints|String Length Restraints]] section on this page for some operational restraints.) But note that in Mono, strings use UTF-16 and occupy two memory bytes per character.


Strings can be concatenated (joined together) using the '''+''' operator.
Strings can be concatenated (joined together) using the '''+''' operator. Note that concatenation cannot be done when defining a string as a global variable, as + is treated as an executable instruction, it's not handled by the compiler. Concatenation can only be done within executable code, i.e. inside a user defined function or in an event.


Some string operations can be done via built-in functions, such as those that can make text all upper and lower case. Other operations, such as replace, left, right, wrap, etc, must be done via functions invented by other LSL users (examples of which are at the bottom of this page.)
Some string operations can be done via built-in functions, such as those that can make text all upper and lower case. Other operations, such as replace, left, right, wrap, etc, must be done via functions invented by other LSL users (examples of which are at the bottom of this page.)
Line 24: Line 24:
|
|
String examples:
String examples:
<lsl>"Hello Avatar!"
<source lang="lsl2">"Hello Avatar!"
"Yes"
"Yes"
"No"
"No"
Line 39: Line 39:
we all scream,
we all scream,
for ice-cream!"
for ice-cream!"
</lsl>
</source>
|}
|}


Line 49: Line 49:
== Variable: string {{LSL Param|name}}; ==
== Variable: string {{LSL Param|name}}; ==
<div style="padding: 0.5em;">
<div style="padding: 0.5em;">
<lsl>string name;</lsl>
<source lang="lsl2">string name;</source>
Declares a variable of type string named '''name''', with the value {{HoverText|""|empty string}}
Declares a variable of type string named '''name''', with the value {{HoverText|""|empty string}}
{|
{|
Line 59: Line 59:
== Variable: string {{LSL Param|name}} {{=}} {{LSL Param|value}}; ==
== Variable: string {{LSL Param|name}} {{=}} {{LSL Param|value}}; ==
<div style="padding: 0.5em;">
<div style="padding: 0.5em;">
<lsl>string name = value;</lsl>
<source lang="lsl2">string name = value;</source>
Declares a variable of type string named '''name''', with the value '''value'''.
Declares a variable of type string named '''name''', with the value '''value'''.
{|
{|
Line 70: Line 70:
== [[Typecast]]: (string){{LSL Param|value_t|value}} ==
== [[Typecast]]: (string){{LSL Param|value_t|value}} ==
<div style="padding: 0.5em;">
<div style="padding: 0.5em;">
<lsl>(string)value</lsl>
<source lang="lsl2">(string)value</source>
Converts '''value''' to a value of type string.
Converts '''value''' to a value of type string.
{|
{|
Line 84: Line 84:
<div id="box" style="padding-left: 0.5em;padding-right: 0.5em;padding-bottom: 0.5em;">
<div id="box" style="padding-left: 0.5em;padding-right: 0.5em;padding-bottom: 0.5em;">
=== Combine: {{LSL Param|value|value1}} + {{LSL Param|value|value2}} ===
=== Combine: {{LSL Param|value|value1}} + {{LSL Param|value|value2}} ===
<lsl>(value1 + value2)</lsl>
<source lang="lsl2">(value1 + value2)</source>
Combines two strings into a single string without modifying the inputs. Appends '''value2''' to '''value1''' and returns the resulting string.
Combines two strings into a single string without modifying the inputs. Appends '''value2''' to '''value1''' and returns the resulting string.
{|
{|
Line 94: Line 94:


=== Comparison: {{LSL Param|value|value1}} <nowiki>==</nowiki> {{LSL Param|value|value2}} ===
=== Comparison: {{LSL Param|value|value1}} <nowiki>==</nowiki> {{LSL Param|value|value2}} ===
<lsl>(value1 == value2)</lsl>
<source lang="lsl2">(value1 == value2)</source>
Compares two strings, returns {{HoverText|one|1}} if same length and same characters, else returns zero.
Compares two strings, returns {{HoverText|one|1}} if same length and same characters, else returns zero.
This operator works exactly like <code>!strcmp('''value1''', '''value2''')</code> in C, thus technically differs from the counterintuitive behavior of the == operator in C and in Java.
This operator works exactly like <code>!strcmp('''value1''', '''value2''')</code> in C, thus technically differs from the counterintuitive behavior of the == operator in C and in Java.
Line 104: Line 104:
<div id="box" style="padding-left: 0.5em;padding-right: 0.5em;padding-bottom: 0.5em;">
<div id="box" style="padding-left: 0.5em;padding-right: 0.5em;padding-bottom: 0.5em;">
=== Comparison: {{LSL Param|value|value1}} != {{LSL Param|value|value2}} ===
=== Comparison: {{LSL Param|value|value1}} != {{LSL Param|value|value2}} ===
<lsl>(value1 != value2)</lsl>
<source lang="lsl2">(value1 != value2)</source>
Compares two strings, returns {{HoverText|zero|0}} if same length and same characters, otherwise non-zero.
Compares two strings, returns {{HoverText|zero|0}} if same length and same characters, otherwise non-zero.
This operator works exactly like <code>strcmp('''value1''', '''value2''')</code> in C, thus technically differs from the counterintuitive behavior of the != operator in C and in Java.
This operator works exactly like <code>strcmp('''value1''', '''value2''')</code> in C, thus technically differs from the counterintuitive behavior of the != operator in C and in Java.
Line 149: Line 149:
That is to say:
That is to say:


<lsl>string hello = "Avatar écoutez";</lsl>
<source lang="lsl2">string hello = "Avatar écoutez";</source>
</div></div>
</div></div>


Line 158: Line 158:


'''Examples'''
'''Examples'''
* [[llSay]] -  When using llSay, any text string being said will be truncated to 1023 [[bytes]] if it is greater than that.
* [[llSay]] -  When using llSay, any text string being said will be truncated to 1024 CHARACTERS, both under LSO and Mono. (That's 2048 bytes of memory space in Mono (UTF-16) ).
* [[llGetNotecardLine]] - When reading in lines from notecards, lines longer than 255 characters will be truncated silently.
* [[llGetNotecardLine]] - When reading in lines from notecards, lines longer than 1023 characters will be truncated silently. (Limit was formerly 255, however with [https://releasenotes.secondlife.com/simulator/2021-10-25.565008.html SLS 565008] this has been increased.)
* [[llDialog]] - If the message or button texts are too long a non-fatal error is produced when the function is called.
* [[llDialog]] - If the message or button texts are too long a non-fatal error is produced when the function is called.


'''Notes'''<br/>
'''Notes'''<br/>
Limits of this type are always documented, an absence of limits in the documentation means there are no known limits (that are outside the norm for the language).
Limits of this type are always documented, an absence of limits in the documentation means there are no known limits (that are outside the norm for the language).
</div></div>
</div>


<div id="box">
<div id="box">
Line 176: Line 176:
The following code ''will'' remove both all double spaces inside a string, as well as any leading and trailing spaces; it will how ever require a substantial amount of memory overhead.
The following code ''will'' remove both all double spaces inside a string, as well as any leading and trailing spaces; it will how ever require a substantial amount of memory overhead.


<lsl>string myTrimmedText = llDumpList2String(llParseString2List(src, [" "], []), " ");</lsl>
<source lang="lsl2">string myTrimmedText = llDumpList2String(llParseString2List(src, [" "], []), " ");</source>


When accepting user text input from chat, a notecard, or a prim name or description, or any other "free-wheeling" source, it's a good idea to always [[llStringTrim]] first before beginning to work with it.
When accepting user text input from chat, a notecard, or a prim name or description, or any other "free-wheeling" source, it's a good idea to always [[llStringTrim]] first before beginning to work with it.
Line 184: Line 184:
== Examples ==
== Examples ==
<div style="padding: 0.5em;">
<div style="padding: 0.5em;">
<lsl>integer int = 48934;
<source lang="lsl2">integer int = 48934;
string str = (string)int;
string str = (string)int;
string str_2;
string str_2;
str_2 = str;</lsl>
str_2 = str;</source>
</div></div>
</div></div>
<div id="box">
<div id="box">
Line 201: Line 201:
!purpose
!purpose
|-
|-
|| [[Chr]] || Returns the Unicode character with the given code. See also [[Ord]].
|| [[Chr]] || <strike>Returns the Unicode character with the given code. See also [[Ord]].</strike> Built-in function: [[llChar]].
|-
|-
|| [[Float2String]] || Allows string output of a float in a tidy text format, with optional rounding.
|| [[Float2String]] || Allows string output of a float in a tidy text format, with optional rounding.
Line 209: Line 209:
|| [[Like]] || See if one word matches part of another.
|| [[Like]] || See if one word matches part of another.
|-
|-
|| [[Ord]] || Returns the ordinal (Unicode code) of a character. See also [[Chr]].
|| [[Ord]] || <strike>Returns the ordinal (Unicode code) of a character. See also [[Chr]].</strike> Built-in function: [[llOrd]].
|-
|-
|| [[RandomString]] || Creates a random string.
|| [[RandomString]] || Creates a random string.
Line 217: Line 217:
|| [[Right]] || Returns text right of a specified separator.
|| [[Right]] || Returns text right of a specified separator.
|-
|-
|| [[Library_Combined_Library#str_replace|str_replace]] || replace all instances of a string with another string in a target string.
|| [[Library_Combined_Library#str_replace|str_replace]] || <strike>Replace all instances of a string with another string in a target string.</strike> Built-in function: [[LlReplaceSubString]].
|-
|-
|| [[Stristr]] || Returns a string from the first occurrence of needle to the end of haystack.
|| [[Stristr]] || Returns a string from the first occurrence of needle to the end of haystack.

Latest revision as of 09:44, 29 October 2023

See also Text.

A string is text data.

String values are enclosed in double quotes when defined in LSL text.

Any character may be used in a string, except for the "NUL" character, though some will need to be escaped (see the Escape Codes section on this page for more info.) The "NUL" character is Unicode value U+0000 and cannot exist in an LSL string. Therefore for example llUnescapeURL("%00") results in an empty string "".

The length of a string is only limited by available script memory. (see the String Length Restraints section on this page for some operational restraints.) But note that in Mono, strings use UTF-16 and occupy two memory bytes per character.

Strings can be concatenated (joined together) using the + operator. Note that concatenation cannot be done when defining a string as a global variable, as + is treated as an executable instruction, it's not handled by the compiler. Concatenation can only be done within executable code, i.e. inside a user defined function or in an event.

Some string operations can be done via built-in functions, such as those that can make text all upper and lower case. Other operations, such as replace, left, right, wrap, etc, must be done via functions invented by other LSL users (examples of which are at the bottom of this page.)

You have no control over the font face, size, weight or colour that string output is displayed in on user screens or on menus. The look of text that displays on screens, such as chat from a text, is controlled by users (though not many change the defaults.) You can only control whether the text is lower or upper case.

(The only time you have control over the colour of displayed text is when it is Floating Text.)


String examples: 

"Hello Avatar!"
"Yes"
"No"
"It's 10 o'clock."
"I am 21 years old!"
"Help " + "me"
EOF

//The following two strings have the same value (i.e. they will both produce text with line breaks in it.)

"I scream,\nyou scream,\nwe all scream,\nfor ice-cream!"
"I scream,
you scream,
we all scream,
for ice-cream!"


Variable: string name;

string name;

Declares a variable of type string named name, with the value ""

• variable name – variable name

Variable: string name = value;

string name = value;

Declares a variable of type string named name, with the value value.

• variable name – variable name
• expression value – string expression or constant

Typecast: (string)value

(string)value

Converts value to a value of type string.

• expression value – expression or constant

Operators

See Operators for more information.

Combine: value1 + value2

(value1 + value2)

Combines two strings into a single string without modifying the inputs. Appends value2 to value1 and returns the resulting string.

• expression value1 – string expression or constant
• expression value2 – string expression or constant

Comparison: value1 == value2

(value1 == value2)

Compares two strings, returns one if same length and same characters, else returns zero. This operator works exactly like !strcmp(value1, value2) in C, thus technically differs from the counterintuitive behavior of the == operator in C and in Java.

• expression value1 – string expression or constant
• expression value2 – string expression or constant

Comparison: value1 != value2

(value1 != value2)

Compares two strings, returns zero if same length and same characters, otherwise non-zero. This operator works exactly like strcmp(value1, value2) in C, thus technically differs from the counterintuitive behavior of the != operator in C and in Java.

• expression value1 – string expression or constant
• expression value2 – string expression or constant

Escape Codes

Substring Replaced with
\t four spaces
\n new line
\" double quote
\\ backslash

Escape codes are translated when the script is compiled; not while it's running. The compiler will ignore any other combination of \ with a character by removing the \. So "\a" means "a". The result is that only strings that are inside your script when it is compiled will get, say, \n turned into a "new line" character. Text you read in from a notecard, chat, http, object name or description, etc, will not be checked for escape codes -- that same \n typed in a notecard doesn't automatically turn into a "new line" character. You'll have to do that yourself, if you really really need it for some reason.

Those who are coming to LSL from such languages as C and Java may find these LSL string escape rules confusing at first. In LSL, "\n" means llUnescapeURL("%0A"), as it does in C and Java, but "\t" means llUnescapeURL("%20%20%20%20") rather than llUnescapeURL("%09"). Additionally there is no "\r" escape code and "\r" will translate to "r" rather than llUnescapeURL("%0D").

For runtime translation of escaped characters try the user function Unescape.

Characters with Accents

It used to be that your script would not compile if you included in it a string containing a character with an accent, such as "écoutez", or punctuation not used in English, such as "¿Entiende?".

Sometime in late spring / early summer 2008, scripts began compiling with accents in text strings.

That is to say: 

string hello = "Avatar écoutez";

String Length Restraints

As noted at the start of this page, the length of a single string is only limited by available script memory. However, there are some operational limitations. Many Communications functions and some other functions also impose limits on input strings. Those limits may result in error messages at runtime or "silent" truncation (i.e. you get no error notice, nor any indication that it has been done.).

Examples

  • llSay - When using llSay, any text string being said will be truncated to 1024 CHARACTERS, both under LSO and Mono. (That's 2048 bytes of memory space in Mono (UTF-16) ).
  • llGetNotecardLine - When reading in lines from notecards, lines longer than 1023 characters will be truncated silently. (Limit was formerly 255, however with SLS 565008 this has been increased.)
  • llDialog - If the message or button texts are too long a non-fatal error is produced when the function is called.

Notes
Limits of this type are always documented, an absence of limits in the documentation means there are no known limits (that are outside the norm for the language).

Trimming a String

Trimming a string used to require user-created functions, such as those created for the purpose in Strife Onizuka's library.

Now, however, there is a native LSL function, llStringTrim, which can be used to remove leading and/or trailing spaces. Note though that it does not remove excess spaces that a user may have entered in the middle of a sentence or string, nor is there any other native LSL function which does.

The following code will remove both all double spaces inside a string, as well as any leading and trailing spaces; it will how ever require a substantial amount of memory overhead. 

string myTrimmedText = llDumpList2String(llParseString2List(src, [" "], []), " ");

When accepting user text input from chat, a notecard, or a prim name or description, or any other "free-wheeling" source, it's a good idea to always llStringTrim first before beginning to work with it.

Examples

integer int = 48934;
string str = (string)int;
string str_2;
str_2 = str;

Useful Functions

User-created utility functions

These functions have been created and contributed by LSL users to perform operations not covered by built-in LSL functions.

function purpose
Chr Returns the Unicode character with the given code. See also Ord. Built-in function: llChar.
Float2String Allows string output of a float in a tidy text format, with optional rounding.
Left Returns text left of a specified separator.
Like See if one word matches part of another.
Ord Returns the ordinal (Unicode code) of a character. See also Chr. Built-in function: llOrd.
RandomString Creates a random string.
RemoveHTMLTags Removes HTML tags from a string ( and newline characters )
Right Returns text right of a specified separator.
str_replace Replace all instances of a string with another string in a target string. Built-in function: LlReplaceSubString.
Stristr Returns a string from the first occurrence of needle to the end of haystack.
SplitLine Insert 'new line' escape codes at certain positions of a string.
WrapText Break text into line lengths of your specification.

Text-Related Items from the Script Library

Name Creator Description
ParseString2List Strife Onizuka Same as llParseString2List and llParseStringKeepNulls, but not limited to 8 spacers or separators. Thus substitute a call to the llParseString2List and llParseStringKeepNulls functions by a call to ParseString2List whenever you have more than 8 separators or more than 8 spacers.
String Compare Xaviar Czervik Compares two strings and reliably returns either 1, -1, or 0 if they are the same.
XyText Xylor Baysklef Display text (up to 10 characters) on a prim. Use as many prims as desired.
XyyyyzText Criz Collins Display text (up to 10 characters) on a prim. Displays different text for each line instead of one single text, that will be broken into the next lines. Watch here for what that means: http://screencast.com/t/1wMLujLcEO
XyzzyText Thraxis Epsilon and Gigs Taggart Display text (up to 10 characters) on a prim. Way more efficient than XyText.

Subcategories

This category has the following 2 subcategories, out of 2 total.

L

S

Retrieved from "https://wiki.secondlife.com/w/index.php?title=Category:LSL_String&oldid=1215251"