Second Life Wiki - User contributions [en]

ListItemReplace

2009-09-26T18:36:44Z

Virtouse Lilienthal: Better use llOwnerSay maybe data is sensitive O.o

{{LSL Header}} __NOTOC__
<div id="box">
== Function: [[list]] ListItemReplace([[list]] {{LSL Param|mylist}}, [[string]] {{LSL Param|element_old}},[[string]] {{LSL Param|element_new}} ); ==
<div style="padding: 0.5em;">
Replaces a single occurrence of something in a list with something else that you specify.

See also: [[List|Lists]]

<lsl>
list ListItemReplace(list mylist,string element_old, string element_new) {
integer placeinlist = llListFindList(mylist, [element_old]);
if ( placeinlist != -1 ) {
return llListReplaceList(mylist, [element_new], placeinlist, placeinlist);
}
llOwnerSay("ERROR: Element '" + element_old + "' not found in list [" + llList2CSV(mylist) + "]" );
return mylist;
}
</lsl>

list myupdatedList = ListItemReplace(mylist,"Brown","Blue");

</div>

{{LSLC|Examples|ListItemReplace}}

ListItemReplace

2009-09-26T18:36:11Z

Virtouse Lilienthal:

{{LSL Header}} __NOTOC__
<div id="box">
== Function: [[list]] ListItemReplace([[list]] {{LSL Param|mylist}}, [[string]] {{LSL Param|element_old}},[[string]] {{LSL Param|element_new}} ); ==
<div style="padding: 0.5em;">
Replaces a single occurrence of something in a list with something else that you specify.

See also: [[List|Lists]]

<lsl>
list ListItemReplace(list mylist,string element_old, string element_new) {
integer placeinlist = llListFindList(mylist, [element_old]);
if ( placeinlist != -1 ) {
return llListReplaceList(mylist, [element_new], placeinlist, placeinlist);
}
llSay(0, "ERROR: Element '" + element_old + "' not found in list [" + llList2CSV(mylist) + "]" );
return mylist;
}
</lsl>

list myupdatedList = ListItemReplace(mylist,"Brown","Blue");

</div>

{{LSLC|Examples|ListItemReplace}}

ListItemReplace

2009-09-26T18:35:14Z

Virtouse Lilienthal:

{{LSL Header}} __NOTOC__
<div id="box">
== Function: [[list]] ListItemReplace([[list]] {{LSL Param|mylist}}, [[string]] {{LSL Param|element_old}},[[string]] {{LSL Param|element_new}} ); ==
<div style="padding: 0.5em;">
Replaces a single occurrence of something in a list with something else that you specify.

See also: [[List|Lists]]

<lsl>
list ListItemReplace(list mylist,string element_old, string element_new) {
integer placeinlist = llListFindList(mylist, [element_old]);
if ( placeinlist != -1 ) {
return llListReplaceList(mylist, [element_new], placeinlist, placeinlist);
}
llSay(0, "ERROR: Element '" + element_old + "' not found in list");
return mylist;
}
</lsl>

list myupdatedList = ListItemReplace(mylist,"Brown","Blue");

</div>

{{LSLC|Examples|ListItemReplace}}

Talk:LLSD

2008-06-27T17:47:49Z

Virtouse Lilienthal: lol I was blind yesterday :P

{{Open Source Talk Page}}

== LLSD JSON-ish notation ==

The login sequence appears to use "binary" LLSD for two of the variables, home and look_at. Unfortunately the format doesn't match up exactly with what is documented on this wiki. Sample values:

{'region_handle':[r255232, r256512], 'position':[r33.6, r33.71, r43.13], 'look_at':[r34.6, r33.71, r43.13]}

[r0.99967899999999998428,r-0.025334599999999998787,r0]

No size values, and the map keys are encased in single quotes. Is this normal? -- {{Unsigned|Eddy Stryker}}

:Oh wow, notation format. Ummmmm, I never documented that, did I. LLSD started it's life as a json-like language, with a well defined serialization which is not actually documented. I'll get on that. [[User:Phoenix Linden|Phoenix Linden]] 16:10, 6 April 2007 (PDT)
:Documentation has been added. [[User:Phoenix Linden|Phoenix Linden]] 17:34, 12 April 2007 (PDT)

== Versioning? ==

Personally I miss a few things here, especially the versioning/compatibility. Sure you can asume that older request just have less keys in a map, and that might work well for things like statistics results. But as soon as you want to call a method, it is much better to make the version obvious. You can encode that in a key/value pair, but it is much better to have that in a fixed element for routing (you can route requests for inventories to different servers, depending on the interface version)

I see a Version:i1 in the notation example for the teleport, which makes it clear, that this element is used already in LL. Maybe it is hard for you to make it to a llsd envelop, but I think you guys will have great use for it.

<pre><llsd>
<method version="1" interface="simstatistics" message="result" />
...</pre>

or something like that.--[[User:Bernd Elswit|Bernd Elswit]] 10:27, 18 May 2007 (PDT)

== Efficient binary support ==

maybe a more efficient binary transport can be added, too? For example Adobe's ASCII85 allows better compression (however you need to escape less-than and ampersand and CDATA). Very efficient could be precalculated huffman tables for the most common file formats.

Sample code at the end of the page: http://www.javaworld.com/javaworld/javatips/jw-javatip117.html

--[[User:Bernd Elswit|Bernd Elswit]] 10:26, 18 May 2007 (PDT)

:Any time that we need to conserve space or cpu resources, we will use zlib routines or [[LLSD#Binary_Serialization|binary serialization]]. [[User:Phoenix Linden|Phoenix Linden]] 12:41, 21 May 2007 (PDT)

== hexadecimal ? ==

does the integer type allow hexadecimal values ? e.g. 0xffcc00 instead of entering 16763904 ?

[[User:SignpostMarv Martin|SignpostMarv Martin]] 09:54, 31 May 2007 (PDT)

== Binary map and array encoding ? ==
The description is not clear how the delimiters for map and array elements should be encoded.
See here:

<pre>
array '[' + htonl(array.length()) + ''(''child0'','' child1'','' ...'')'' + ']'

map '{' + htonl(map.length()) + ''((''key0'',''value0''),(''key1, value1''),'' ...'')'' + '}'
</pre>

Especially the binary encoding of the <pre>''</pre> marked values is not defined. As I am sitting at an implementation of this, I will try with the supposed reference implementation llsd.py and see what that actually does for this part.
--[[User:Leffard Lassard|Leffard Lassard]] 10:04, 27 March 2008 (PDT)

From my own research it is more like this:

<pre>
array '[' + htonl(array.length()) + child0 + child1 + ']'

map '{' + htonl(map.length()) + 'k' + htonl(key0.length) + key0 + value0 + 'k' + htonl(key1.length) + key1 + value 1 ... + '}'
</pre>

--[[User:Leffard Lassard|Leffard Lassard]] 11:26, 28 March 2008 (PDT)

== XML <-> Notation? ==

The XML format is, let's face it, not fun to read or write, for humans, in those weird cases where humans have to. Is there a serialization converter, somewhere, or should I just rig my own? --[[User:Ky Aska|Ky Aska]] 06:12, 3 June 2008 (PDT)

Talk:LLSD

2008-06-26T22:03:51Z

Virtouse Lilienthal: /* LLSD JSON-ish notation */

{{Open Source Talk Page}}

== LLSD JSON-ish notation ==

The login sequence appears to use "binary" LLSD for two of the variables, home and look_at. Unfortunately the format doesn't match up exactly with what is documented on this wiki. Sample values:

{'region_handle':[r255232, r256512], 'position':[r33.6, r33.71, r43.13], 'look_at':[r34.6, r33.71, r43.13]}

[r0.99967899999999998428,r-0.025334599999999998787,r0]

No size values, and the map keys are encased in single quotes. Is this normal? -- {{Unsigned|Eddy Stryker}}

:Oh wow, notation format. Ummmmm, I never documented that, did I. LLSD started it's life as a json-like language, with a well defined serialization which is not actually documented. I'll get on that. [[User:Phoenix Linden|Phoenix Linden]] 16:10, 6 April 2007 (PDT)
:Documentation has been added. [[User:Phoenix Linden|Phoenix Linden]] 17:34, 12 April 2007 (PDT)

Something is weird. You're documenting that the LLSD/Notation format can have the following values for booleans:
true '1' | 't' | 'T' | 'true' | 'TRUE'
false '0' | 'f' | 'F' | 'false' | 'FALSE'

But actually you're not even handling anything but 1 and 0 yourself?
So, what is with the other values?

--[[User:Virtouse Lilienthal|Virtouse Lilienthal]] 15:03, 26 June 2008 (PDT)

== Versioning? ==

Personally I miss a few things here, especially the versioning/compatibility. Sure you can asume that older request just have less keys in a map, and that might work well for things like statistics results. But as soon as you want to call a method, it is much better to make the version obvious. You can encode that in a key/value pair, but it is much better to have that in a fixed element for routing (you can route requests for inventories to different servers, depending on the interface version)

I see a Version:i1 in the notation example for the teleport, which makes it clear, that this element is used already in LL. Maybe it is hard for you to make it to a llsd envelop, but I think you guys will have great use for it.

<pre><llsd>
<method version="1" interface="simstatistics" message="result" />
...</pre>

or something like that.--[[User:Bernd Elswit|Bernd Elswit]] 10:27, 18 May 2007 (PDT)

== Efficient binary support ==

maybe a more efficient binary transport can be added, too? For example Adobe's ASCII85 allows better compression (however you need to escape less-than and ampersand and CDATA). Very efficient could be precalculated huffman tables for the most common file formats.

Sample code at the end of the page: http://www.javaworld.com/javaworld/javatips/jw-javatip117.html

--[[User:Bernd Elswit|Bernd Elswit]] 10:26, 18 May 2007 (PDT)

:Any time that we need to conserve space or cpu resources, we will use zlib routines or [[LLSD#Binary_Serialization|binary serialization]]. [[User:Phoenix Linden|Phoenix Linden]] 12:41, 21 May 2007 (PDT)

== hexadecimal ? ==

does the integer type allow hexadecimal values ? e.g. 0xffcc00 instead of entering 16763904 ?

[[User:SignpostMarv Martin|SignpostMarv Martin]] 09:54, 31 May 2007 (PDT)

== Binary map and array encoding ? ==
The description is not clear how the delimiters for map and array elements should be encoded.
See here:

<pre>
array '[' + htonl(array.length()) + ''(''child0'','' child1'','' ...'')'' + ']'

map '{' + htonl(map.length()) + ''((''key0'',''value0''),(''key1, value1''),'' ...'')'' + '}'
</pre>

Especially the binary encoding of the <pre>''</pre> marked values is not defined. As I am sitting at an implementation of this, I will try with the supposed reference implementation llsd.py and see what that actually does for this part.
--[[User:Leffard Lassard|Leffard Lassard]] 10:04, 27 March 2008 (PDT)

From my own research it is more like this:

<pre>
array '[' + htonl(array.length()) + child0 + child1 + ']'

map '{' + htonl(map.length()) + 'k' + htonl(key0.length) + key0 + value0 + 'k' + htonl(key1.length) + key1 + value 1 ... + '}'
</pre>

--[[User:Leffard Lassard|Leffard Lassard]] 11:26, 28 March 2008 (PDT)

== XML <-> Notation? ==

The XML format is, let's face it, not fun to read or write, for humans, in those weird cases where humans have to. Is there a serialization converter, somewhere, or should I just rig my own? --[[User:Ky Aska|Ky Aska]] 06:12, 3 June 2008 (PDT)