LlJsonGetValue - Revision history

SuzannaLinn Resident at 10:58, 5 June 2026

2026-06-05T10:58:26Z

← Older revision		Revision as of 03:58, 5 June 2026
Line 3:		Line 3:
	\|func_id=\|func_sleep=0.0\|func_energy=10.0		\|func_id=\|func_sleep=0.0\|func_energy=10.0
	\|func=		\|func=
	~~lJsonGetValue~~\|return_type=string\|p1_type=string\|p1_name=json\|p2_type=list\|p2_name=specifiers		llJsonGetValue\|return_type=string\|p1_type=string\|p1_name=json\|p2_type=list\|p2_name=specifiers
	\|func_desc=Gets the value indicated by specifiers from the [http://json.org json] string.		\|func_desc=Gets the value indicated by specifiers from the [http://json.org json] string.
	\|return_text=made by parsing '''json''', a string representing json and traversing as specified by '''specifiers'''.		\|return_text=made by parsing '''json''', a string representing json and traversing as specified by '''specifiers'''.

Gwyneth Llewelyn: Very minor cosmetic changes, just to test out what's wrong with Template:LSL_Funtion

2025-06-20T15:17:36Z

Very minor cosmetic changes, just to test out what's wrong with Template:LSL_Funtion

← Older revision		Revision as of 08:17, 20 June 2025
Line 1:		Line 1:
	{{LSL Function		{{LSL Function
	\|inject-1={{Issues/BUG-3692}}		\|inject-1={{Issues\|BUG-3692}}
	\|func_id=\|func_sleep=0.0\|func_energy=10.0		\|func_id=\|func_sleep=0.0\|func_energy=10.0
	\|func=~~llJsonGetValue~~\|return_type=string\|p1_type=string\|p1_name=json\|p2_type=list\|p2_name=specifiers		\|func=
			lJsonGetValue\|return_type=string\|p1_type=string\|p1_name=json\|p2_type=list\|p2_name=specifiers
	\|func_desc=Gets the value indicated by specifiers from the [http://json.org json] string.		\|func_desc=Gets the value indicated by specifiers from the [http://json.org json] string.
	\|return_text=made by parsing '''json''', a string representing json and traversing as specified by '''specifiers'''.		\|return_text=made by parsing '''json''', a string representing json and traversing as specified by '''specifiers'''.
Line 9:		Line 10:
	\|constants		\|constants
	\|caveats=		\|caveats=
	* Manual definition of JSON syntax within LSL does not always parse in the expected way, so be careful to avoid using syntax characters anywhere other than where needed (for example, inside a string.); alternately escape the syntax character and use [[llUnescapeURL]] on the retrieved string to convert it back - See bugs.		* Manual definition of JSON syntax within LSL does not always parse in the expected way, so be careful to avoid using syntax characters anywhere other than where needed (for example, inside a string.); alternately escape the syntax character and use [[llUnescapeURL]] on the retrieved string to convert it back - See [[#bugs]].
	{{KBwarning\|The below comment in regards to speed cannot be assumed to be true on all server versions and in all environments. '''Always test execution speed claims for yourself.'''}}		{{KBwarning\|The below comment in regards to speed cannot be assumed to be true on all server versions and in all environments. '''Always test execution speed claims for yourself.'''}}
	* As of Second Life Server 2024-06-11.9458617693, benchmark testing in a 99%+ scripts run environment resulted in the following conclusions with a 3-element array cast to either JSON or CSV:		* As of Second Life Server 2024-06-11.9458617693, benchmark testing in a 99%+ scripts run environment resulted in the following conclusions with a 3-element array cast to either JSON or CSV:
	** [[llJsonGetValue]] takes approximately 2-3 ms per call to execute regardless of depth, making it a faster option for reading a single element from a dataset.		** [[llJsonGetValue]] takes approximately 2-3 ms per call to execute regardless of depth, making it a faster option for reading a single element from a dataset.
	** [[llParseStringKeepNulls]] takes approximately 5 ms to execute, while each subsequent [[llList2String]] takes approximately 0.5 ms to execute, making it a faster option for reading more than 2 elements from a dataset.		** [[llParseStringKeepNulls]] takes approximately 5 ms to execute, while each subsequent [[llList2String]] takes approximately 0.5 ms to execute, making it a faster option for reading more than 2 elements from a dataset.
	* This function will convert the occurrence of a \n to a line feed and a \t to U+0009.		* This function will convert the occurrence of a <code>\n</code> to a line feed and a <code>\t</code> to <code>U+0009</code>.
	\|examples=		\|examples=
	<syntaxhighlight lang="lsl2">		<syntaxhighlight lang="lsl2">
Line 30:		Line 31:

	</syntaxhighlight>		</syntaxhighlight>

	<syntaxhighlight lang="lsl2">		<syntaxhighlight lang="lsl2">
	JGetValTest(){		JGetValTest(){
Line 75:		Line 77:
	\|cat4=JSON		\|cat4=JSON
	\|history = Date of Release [[ Release_Notes/Second_Life_Server/13#13.05.20.276191 \| 20/05/2013 ]]		\|history = Date of Release [[ Release_Notes/Second_Life_Server/13#13.05.20.276191 \| 20/05/2013 ]]
	\|~~inject~~-2={{Issues\|BUG-6495\|JSON does not correctly handle ] inside strings nested within arrays or } inside strings nested within objects\|type=bug\|status=ack}}		\|Inject-2={{Issues\|BUG-6495\|JSON does not correctly handle ] inside strings nested within arrays or } inside strings nested within objects\|type=bug\|status=ack}}
	}}		}}

Gwyneth Llewelyn: There is something wrong with the LSL Function `inject-N` parameters, as well as with the `bugs` parameter, but I have no idea why!

2025-06-20T15:00:52Z

There is something wrong with the LSL Function `inject-N` parameters, as well as with the `bugs` parameter, but I have no idea why!

← Older revision		Revision as of 08:00, 20 June 2025
Line 1:		Line 1:
	{{LSL Function		{{LSL Function
	\|inject-2={{Issues/BUG-3692}}		\|inject-1={{Issues/BUG-3692}}
	\|func_id=\|func_sleep=0.0\|func_energy=10.0		\|func_id=\|func_sleep=0.0\|func_energy=10.0
	\|func=llJsonGetValue\|return_type=string\|p1_type=string\|p1_name=json\|p2_type=list\|p2_name=specifiers		\|func=llJsonGetValue\|return_type=string\|p1_type=string\|p1_name=json\|p2_type=list\|p2_name=specifiers

Lucia Nightfire: Added caveat mentioning that this function converts \n and \t.

2024-12-24T05:05:32Z

Added caveat mentioning that this function converts \n and \t.

← Older revision		Revision as of 22:05, 23 December 2024
Line 14:		Line 14:
	** [[llJsonGetValue]] takes approximately 2-3 ms per call to execute regardless of depth, making it a faster option for reading a single element from a dataset.		** [[llJsonGetValue]] takes approximately 2-3 ms per call to execute regardless of depth, making it a faster option for reading a single element from a dataset.
	** [[llParseStringKeepNulls]] takes approximately 5 ms to execute, while each subsequent [[llList2String]] takes approximately 0.5 ms to execute, making it a faster option for reading more than 2 elements from a dataset.		** [[llParseStringKeepNulls]] takes approximately 5 ms to execute, while each subsequent [[llList2String]] takes approximately 0.5 ms to execute, making it a faster option for reading more than 2 elements from a dataset.
			* This function will convert the occurrence of a \n to a line feed and a \t to U+0009.
	\|examples=		\|examples=
	<syntaxhighlight lang="lsl2">		<syntaxhighlight lang="lsl2">

Nelson Jenkins: a word

2024-08-18T23:26:38Z

a word

← Older revision		Revision as of 16:26, 18 August 2024
Line 12:		Line 12:
	{{KBwarning\|The below comment in regards to speed cannot be assumed to be true on all server versions and in all environments. '''Always test execution speed claims for yourself.'''}}		{{KBwarning\|The below comment in regards to speed cannot be assumed to be true on all server versions and in all environments. '''Always test execution speed claims for yourself.'''}}
	* As of Second Life Server 2024-06-11.9458617693, benchmark testing in a 99%+ scripts run environment resulted in the following conclusions with a 3-element array cast to either JSON or CSV:		* As of Second Life Server 2024-06-11.9458617693, benchmark testing in a 99%+ scripts run environment resulted in the following conclusions with a 3-element array cast to either JSON or CSV:
	** [[llJsonGetValue]] takes approximately 2-3 ms per call to execute regardless of depth, making it a faster option for reading a single element from ~~JSON~~.		** [[llJsonGetValue]] takes approximately 2-3 ms per call to execute regardless of depth, making it a faster option for reading a single element from a dataset.
	** [[llParseStringKeepNulls]] takes approximately 5 ms to execute, while each subsequent [[llList2String]] takes approximately 0.5 ms to execute, making it a faster option reading more than 2 elements from ~~JSON~~.		** [[llParseStringKeepNulls]] takes approximately 5 ms to execute, while each subsequent [[llList2String]] takes approximately 0.5 ms to execute, making it a faster option for reading more than 2 elements from a dataset.
	\|examples=		\|examples=
	<syntaxhighlight lang="lsl2">		<syntaxhighlight lang="lsl2">

Nelson Jenkins: added results of benchmarking llJsonGetValue vs. llParseStringKeepNulls/llList2String

2024-08-18T23:25:17Z

added results of benchmarking llJsonGetValue vs. llParseStringKeepNulls/llList2String

← Older revision		Revision as of 16:25, 18 August 2024
Line 10:		Line 10:
	\|caveats=		\|caveats=
	* Manual definition of JSON syntax within LSL does not always parse in the expected way, so be careful to avoid using syntax characters anywhere other than where needed (for example, inside a string.); alternately escape the syntax character and use [[llUnescapeURL]] on the retrieved string to convert it back - See bugs.		* Manual definition of JSON syntax within LSL does not always parse in the expected way, so be careful to avoid using syntax characters anywhere other than where needed (for example, inside a string.); alternately escape the syntax character and use [[llUnescapeURL]] on the retrieved string to convert it back - See bugs.
	{{KBwarning\|The below comment in regards to speed ~~is unverified on modern simulator versions, and thus~~ cannot be assumed to be true. '''Always test execution speed claims for yourself.'''}}		{{KBwarning\|The below comment in regards to speed cannot be assumed to be true on all server versions and in all environments. '''Always test execution speed claims for yourself.'''}}
	* [[llJsonGetValue]] ~~is significantly slower than~~ reading a ~~value~~ from ~~a list with [[llList2String]]~~. ~~But with~~ [[~~llList2String~~]], ~~you will need to parse your string and convert it to list. [[llJsonGetValue]] is significantly faster when you will need to parse your string: for instance by <code>~~[[llList2String]]~~([[llParseString2List]]( yourstring, [delimiters], [spacers]), N );</code> When you need~~ to ~~iterate intensively~~, ~~think about [[llJson2List]]~~.		* As of Second Life Server 2024-06-11.9458617693, benchmark testing in a 99%+ scripts run environment resulted in the following conclusions with a 3-element array cast to either JSON or CSV:
			** [[llJsonGetValue]] takes approximately 2-3 ms per call to execute regardless of depth, making it a faster option for reading a single element from JSON.
			** [[llParseStringKeepNulls]] takes approximately 5 ms to execute, while each subsequent [[llList2String]] takes approximately 0.5 ms to execute, making it a faster option reading more than 2 elements from JSON.
	\|examples=		\|examples=
	<syntaxhighlight lang="lsl2">		<syntaxhighlight lang="lsl2">

Jenna Huntsman: Add caveat about manual syntax definition and conflicts with syntax characters intended for use within a string.

2022-08-25T18:11:53Z

Add caveat about manual syntax definition and conflicts with syntax characters intended for use within a string.

← Older revision		Revision as of 11:11, 25 August 2022
Line 9:		Line 9:
	\|constants		\|constants
	\|caveats=		\|caveats=
			* Manual definition of JSON syntax within LSL does not always parse in the expected way, so be careful to avoid using syntax characters anywhere other than where needed (for example, inside a string.); alternately escape the syntax character and use [[llUnescapeURL]] on the retrieved string to convert it back - See bugs.
	{{KBwarning\|The below comment in regards to speed is unverified on modern simulator versions, and thus cannot be assumed to be true. '''Always test execution speed claims for yourself.'''}}		{{KBwarning\|The below comment in regards to speed is unverified on modern simulator versions, and thus cannot be assumed to be true. '''Always test execution speed claims for yourself.'''}}
	* [[llJsonGetValue]] is significantly slower than reading a value from a list with [[llList2String]]. But with [[llList2String]], you will need to parse your string and convert it to list. [[llJsonGetValue]] is significantly faster when you will need to parse your string: for instance by <code>[[llList2String]]([[llParseString2List]]( yourstring, [delimiters], [spacers]), N );</code> When you need to iterate intensively, think about [[llJson2List]].		* [[llJsonGetValue]] is significantly slower than reading a value from a list with [[llList2String]]. But with [[llList2String]], you will need to parse your string and convert it to list. [[llJsonGetValue]] is significantly faster when you will need to parse your string: for instance by <code>[[llList2String]]([[llParseString2List]]( yourstring, [delimiters], [spacers]), N );</code> When you need to iterate intensively, think about [[llJson2List]].
Line 71:		Line 72:
	\|cat4=JSON		\|cat4=JSON
	\|history = Date of Release [[ Release_Notes/Second_Life_Server/13#13.05.20.276191 \| 20/05/2013 ]]		\|history = Date of Release [[ Release_Notes/Second_Life_Server/13#13.05.20.276191 \| 20/05/2013 ]]
			\|inject-2={{Issues\|BUG-6495\|JSON does not correctly handle ] inside strings nested within arrays or } inside strings nested within objects\|type=bug\|status=ack}}
	}}		}}

Jenna Huntsman: Formatting cleanup.

2022-06-05T19:59:57Z

Formatting cleanup.

← Older revision		Revision as of 12:59, 5 June 2022
Line 6:		Line 6:
	\|return_text=made by parsing '''json''', a string representing json and traversing as specified by '''specifiers'''.		\|return_text=made by parsing '''json''', a string representing json and traversing as specified by '''specifiers'''.
	\|func_footnote=When the input is invalid or no result can be found this function returns [[JSON_INVALID]]. If the result is <code>null</code> the function returns [[JSON_NULL]].		\|func_footnote=When the input is invalid or no result can be found this function returns [[JSON_INVALID]]. If the result is <code>null</code> the function returns [[JSON_NULL]].
	\|spec=See [[Json_usage_in_LSL]]		\|spec=See [[Json_usage_in_LSL\|Json usage in LSL]]
	\|constants		\|constants
	\|caveats=		\|caveats=

Jenna Huntsman: Add a note to the current caveat telling users that the claims of speed are out-of-date.

2022-06-05T17:06:51Z

Add a note to the current caveat telling users that the claims of speed are out-of-date.

← Older revision		Revision as of 10:06, 5 June 2022
Line 9:		Line 9:
	\|constants		\|constants
	\|caveats=		\|caveats=
			{{KBwarning\|The below comment in regards to speed is unverified on modern simulator versions, and thus cannot be assumed to be true. '''Always test execution speed claims for yourself.'''}}
	* [[llJsonGetValue]] is significantly slower than reading a value from a list with [[llList2String]]. But with [[llList2String]], you will need to parse your string and convert it to list. [[llJsonGetValue]] is significantly faster when you will need to parse your string: for instance by <code>[[llList2String]]([[llParseString2List]]( yourstring, [delimiters], [spacers]), N );</code> When you need to iterate intensively, think about [[llJson2List]].		* [[llJsonGetValue]] is significantly slower than reading a value from a list with [[llList2String]]. But with [[llList2String]], you will need to parse your string and convert it to list. [[llJsonGetValue]] is significantly faster when you will need to parse your string: for instance by <code>[[llList2String]]([[llParseString2List]]( yourstring, [delimiters], [spacers]), N );</code> When you need to iterate intensively, think about [[llJson2List]].
	\|examples=		\|examples=
	<~~source~~ lang="lsl2">		<syntaxhighlight lang="lsl2">
	default {		default {
	state_entry() {		state_entry() {
Line 24:		Line 25:
	}		}

	</~~source~~>		</syntaxhighlight>
	<~~source~~ lang="lsl2">		<syntaxhighlight lang="lsl2">
	JGetValTest(){		JGetValTest(){
	string j="[[1,2],[4,5,6]]"; //JSON may be written directly as a string like this in sl.		string j="[[1,2],[4,5,6]]"; //JSON may be written directly as a string like this in sl.
Line 51:		Line 52:
	// a JSON string, just values to test against.		// a JSON string, just values to test against.
	}		}
	</~~source~~>		</syntaxhighlight>
	See also [[llJsonValueType]] for examples where the value type is checked before getting the value as that type.		See also [[llJsonValueType]] for examples where the value type is checked before getting the value as that type.
	\|helpers		\|helpers

Strife Onizuka at 16:50, 9 May 2015

2015-05-09T16:50:38Z

← Older revision		Revision as of 09:50, 9 May 2015
Line 8:		Line 8:
	\|spec=See [[Json_usage_in_LSL]]		\|spec=See [[Json_usage_in_LSL]]
	\|constants		\|constants
			\|caveats=
			* [[llJsonGetValue]] is significantly slower than reading a value from a list with [[llList2String]]. But with [[llList2String]], you will need to parse your string and convert it to list. [[llJsonGetValue]] is significantly faster when you will need to parse your string: for instance by <code>[[llList2String]]([[llParseString2List]]( yourstring, [delimiters], [spacers]), N );</code> When you need to iterate intensively, think about [[llJson2List]].
	\|examples=		\|examples=
	<source lang="lsl2">		<source lang="lsl2">
Line 51:		Line 53:
	</source>		</source>
	See also [[llJsonValueType]] for examples where the value type is checked before getting the value as that type.		See also [[llJsonValueType]] for examples where the value type is checked before getting the value as that type.

	~~\|caveats=~~

	* [[llJsonGetValue]] is significantly slower than reading a value from a list with [[llList2String]]. But with [[llList2String]], you will need to parse your string and convert it to list. [[llJsonGetValue]] is significantly faster when you will need to parse your string: for instance by <code>llList2String( llParseString2List( yourstring, [ delimiters], [ spacers]), N );</code> When you need to iterate intensively, think about [[llJson2List]].
	\|helpers		\|helpers
	\|also_functions={{LSL DefineRow\|\|[[llList2Json]]\|}}		\|also_functions={{LSL DefineRow\|\|[[llList2Json]]\|}}