Lines Matching +refs:format +refs:decode
24 $perl_scalar = $coder->decode ($unicode_json_text);
92 You can choose between the most compact guaranteed-single-line format
93 possible (nice for simple line-based protocols), a pure-ASCII format
95 Unicode range), or a pretty-printed format (for when you want to read that
142 $perl_scalar = JSON::XS->new->utf8->decode ($json_text)
229 in a faster and more compact format.
248 latin1-encoded JSON text or a native Unicode string. The C<decode> method
249 will not be affected in any way by this flag, as C<decode> by default
275 C<decode> method expects to be handled an UTF-8-encoded string. Please
282 string as a (non-encoded) Unicode string, while C<decode> expects thus a
294 Example, decode UTF-32LE-encoded JSON:
297 $object = JSON::XS->new->decode (decode "UTF-32LE", $jsontext);
321 format as output, putting every array member or object/hash key-value pair
368 If C<$enable> is true (or missing), then C<decode> will accept some
375 If C<$enable> is false (the default), then C<decode> will only accept
438 which is an extension to RFC4627. Likewise, C<decode> will accept those JSON
443 or array. Likewise, C<decode> will croak if given something that is not a
465 This option does not affect C<decode> in any way, and it is recommended to
482 This setting has no effect on C<decode>.
506 This setting has no effect on C<decode>.
517 a nonstandard tagged JSON value (that JSON decoders cannot decode).
519 It also causes C<decode> to parse such tagged JSON values and deserialise
524 in C<decode>, as if tags were not part of the grammar.
528 When C<$coderef> is specified, it will be called from C<decode> each
538 be removed and C<decode> will not change the deserialised hash in any
545 $js->decode ('[{}]')
548 $js->decode ('{"a":1, "b":2}');
578 Example, decode JSON objects of the form C<< { "__widget__" => <id> } >>
587 ->decode ('{"__widget__": 5')
608 C<encode> or C<decode> to their minimum size possible. This can save
620 be shrunk-to-fit, while all strings generated by C<decode> will also be
661 being attempted. The default is C<0>, meaning no limit. When C<decode>
663 attempt to decode the string but throw an exception. This setting has no
676 =item $perl_scalar = $json->decode ($json_text)
683 This works like the C<decode> method, but instead of raising an exception
703 a full JSON object, which it then can decode. This process is similar to
737 this method will croak just as C<decode> would do (one can then use
786 each successful decode.
795 concatenate them back to back and still decode them perfectly. This does
806 works similarly to C<decode_prefix>: We want to decode the JSON object at
836 # split and decode as many requests as possible
869 JSON decode the array elements, which are all full JSON objects on their
1146 encoded as a tagged JSON value in the following format:
1235 by C<decode>) is UTF-8 encoded or not, while C<latin1> and C<ascii> only
1241 C<encode> and C<decode>, that is, texts encoded with any combination of
1257 When C<utf8> is disabled (the default), then C<encode>/C<decode> generate
1273 If the C<utf8>-flag is enabled, C<encode>/C<decode> will encode all
1304 Surprisingly, C<decode> will ignore these flags and so treat all input
1306 to decode ISO-8859-1- and ASCII-encoded strings, as both strict subsets of
1307 Unicode. If it is enabled, you can correctly decode UTF-8 encoded strings.
1472 module | encode | decode |
1492 module | encode | decode |
1508 (such as JSON::PC) seem to decode faster than JSON::XS, but the result
1510 to decode or encode properly, so it was impossible to prepare a fair
1527 usually a good indication of the size of the resources required to decode
1534 machine with 8MB of stack size I can decode around 180k nested arrays but