… | |
… | |
40 | Beginning with version 2.0 of the JSON module, when both JSON and |
40 | Beginning with version 2.0 of the JSON module, when both JSON and |
41 | JSON::XS are installed, then JSON will fall back on JSON::XS (this can be |
41 | JSON::XS are installed, then JSON will fall back on JSON::XS (this can be |
42 | overridden) with no overhead due to emulation (by inheriting constructor |
42 | overridden) with no overhead due to emulation (by inheriting constructor |
43 | and methods). If JSON::XS is not available, it will fall back to the |
43 | and methods). If JSON::XS is not available, it will fall back to the |
44 | compatible JSON::PP module as backend, so using JSON instead of JSON::XS |
44 | compatible JSON::PP module as backend, so using JSON instead of JSON::XS |
45 | gives you a portable JSON API that can be fast when you need and doesn't |
45 | gives you a portable JSON API that can be fast when you need it and |
46 | require a C compiler when that is a problem. |
46 | doesn't require a C compiler when that is a problem. |
47 | |
47 | |
48 | As this is the n-th-something JSON module on CPAN, what was the reason |
48 | As this is the n-th-something JSON module on CPAN, what was the reason |
49 | to write yet another JSON module? While it seems there are many JSON |
49 | to write yet another JSON module? While it seems there are many JSON |
50 | modules, none of them correctly handle all corner cases, and in most cases |
50 | modules, none of them correctly handle all corner cases, and in most cases |
51 | their maintainers are unresponsive, gone missing, or not listening to bug |
51 | their maintainers are unresponsive, gone missing, or not listening to bug |
… | |
… | |
101 | |
101 | |
102 | package JSON::XS; |
102 | package JSON::XS; |
103 | |
103 | |
104 | use common::sense; |
104 | use common::sense; |
105 | |
105 | |
106 | our $VERSION = 3.01; |
106 | our $VERSION = 3.04; |
107 | our @ISA = qw(Exporter); |
107 | our @ISA = qw(Exporter); |
108 | |
108 | |
109 | our @EXPORT = qw(encode_json decode_json); |
109 | our @EXPORT = qw(encode_json decode_json); |
110 | |
110 | |
111 | use Exporter; |
111 | use Exporter; |
… | |
… | |
131 | |
131 | |
132 | Except being faster. |
132 | Except being faster. |
133 | |
133 | |
134 | =item $perl_scalar = decode_json $json_text |
134 | =item $perl_scalar = decode_json $json_text |
135 | |
135 | |
136 | The opposite of C<encode_json>: expects an UTF-8 (binary) string and tries |
136 | The opposite of C<encode_json>: expects a UTF-8 (binary) string and tries |
137 | to parse that as an UTF-8 encoded JSON text, returning the resulting |
137 | to parse that as a UTF-8 encoded JSON text, returning the resulting |
138 | reference. Croaks on error. |
138 | reference. Croaks on error. |
139 | |
139 | |
140 | This function call is functionally identical to: |
140 | This function call is functionally identical to: |
141 | |
141 | |
142 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
142 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
… | |
… | |
202 | =over 4 |
202 | =over 4 |
203 | |
203 | |
204 | =item $json = new JSON::XS |
204 | =item $json = new JSON::XS |
205 | |
205 | |
206 | Creates a new JSON::XS object that can be used to de/encode JSON |
206 | Creates a new JSON::XS object that can be used to de/encode JSON |
207 | strings. All boolean flags described below are by default I<disabled>. |
207 | strings. All boolean flags described below are by default I<disabled> |
|
|
208 | (with the exception of C<allow_nonref>, which defaults to I<enabled> since |
|
|
209 | version C<4.0>). |
208 | |
210 | |
209 | The mutators for flags all return the JSON object again and thus calls can |
211 | The mutators for flags all return the JSON object again and thus calls can |
210 | be chained: |
212 | be chained: |
211 | |
213 | |
212 | my $json = JSON::XS->new->utf8->space_after->encode ({a => [1,2]}) |
214 | my $json = JSON::XS->new->utf8->space_after->encode ({a => [1,2]}) |
… | |
… | |
270 | |
272 | |
271 | =item $enabled = $json->get_utf8 |
273 | =item $enabled = $json->get_utf8 |
272 | |
274 | |
273 | If C<$enable> is true (or missing), then the C<encode> method will encode |
275 | If C<$enable> is true (or missing), then the C<encode> method will encode |
274 | the JSON result into UTF-8, as required by many protocols, while the |
276 | the JSON result into UTF-8, as required by many protocols, while the |
275 | C<decode> method expects to be handled an UTF-8-encoded string. Please |
277 | C<decode> method expects to be handed a UTF-8-encoded string. Please |
276 | note that UTF-8-encoded strings do not contain any characters outside the |
278 | note that UTF-8-encoded strings do not contain any characters outside the |
277 | range C<0..255>, they are thus useful for bytewise/binary I/O. In future |
279 | range C<0..255>, they are thus useful for bytewise/binary I/O. In future |
278 | versions, enabling this option might enable autodetection of the UTF-16 |
280 | versions, enabling this option might enable autodetection of the UTF-16 |
279 | and UTF-32 encoding families, as described in RFC4627. |
281 | and UTF-32 encoding families, as described in RFC4627. |
280 | |
282 | |
… | |
… | |
365 | |
367 | |
366 | =item $enabled = $json->get_relaxed |
368 | =item $enabled = $json->get_relaxed |
367 | |
369 | |
368 | If C<$enable> is true (or missing), then C<decode> will accept some |
370 | If C<$enable> is true (or missing), then C<decode> will accept some |
369 | extensions to normal JSON syntax (see below). C<encode> will not be |
371 | extensions to normal JSON syntax (see below). C<encode> will not be |
370 | affected in anyway. I<Be aware that this option makes you accept invalid |
372 | affected in any way. I<Be aware that this option makes you accept invalid |
371 | JSON texts as if they were valid!>. I suggest only to use this option to |
373 | JSON texts as if they were valid!>. I suggest only to use this option to |
372 | parse application-specific files written by humans (configuration files, |
374 | parse application-specific files written by humans (configuration files, |
373 | resource files etc.) |
375 | resource files etc.) |
374 | |
376 | |
375 | If C<$enable> is false (the default), then C<decode> will only accept |
377 | If C<$enable> is false (the default), then C<decode> will only accept |
… | |
… | |
404 | [ |
406 | [ |
405 | 1, # this comment not allowed in JSON |
407 | 1, # this comment not allowed in JSON |
406 | # neither this one... |
408 | # neither this one... |
407 | ] |
409 | ] |
408 | |
410 | |
|
|
411 | =item * literal ASCII TAB characters in strings |
|
|
412 | |
|
|
413 | Literal ASCII TAB characters are now allowed in strings (and treated as |
|
|
414 | C<\t>). |
|
|
415 | |
|
|
416 | [ |
|
|
417 | "Hello\tWorld", |
|
|
418 | "Hello<TAB>World", # literal <TAB> would not normally be allowed |
|
|
419 | ] |
|
|
420 | |
409 | =back |
421 | =back |
410 | |
422 | |
411 | =item $json = $json->canonical ([$enable]) |
423 | =item $json = $json->canonical ([$enable]) |
412 | |
424 | |
413 | =item $enabled = $json->get_canonical |
425 | =item $enabled = $json->get_canonical |
… | |
… | |
431 | |
443 | |
432 | =item $json = $json->allow_nonref ([$enable]) |
444 | =item $json = $json->allow_nonref ([$enable]) |
433 | |
445 | |
434 | =item $enabled = $json->get_allow_nonref |
446 | =item $enabled = $json->get_allow_nonref |
435 | |
447 | |
|
|
448 | Unlike other boolean options, this opotion is enabled by default beginning |
|
|
449 | with version C<4.0>. See L<SECURITY CONSIDERATIONS> for the gory details. |
|
|
450 | |
436 | If C<$enable> is true (or missing), then the C<encode> method can convert a |
451 | If C<$enable> is true (or missing), then the C<encode> method can convert a |
437 | non-reference into its corresponding string, number or null JSON value, |
452 | non-reference into its corresponding string, number or null JSON value, |
438 | which is an extension to RFC4627. Likewise, C<decode> will accept those JSON |
453 | which is an extension to RFC4627. Likewise, C<decode> will accept those JSON |
439 | values instead of croaking. |
454 | values instead of croaking. |
440 | |
455 | |
441 | If C<$enable> is false, then the C<encode> method will croak if it isn't |
456 | If C<$enable> is false, then the C<encode> method will croak if it isn't |
442 | passed an arrayref or hashref, as JSON texts must either be an object |
457 | passed an arrayref or hashref, as JSON texts must either be an object |
443 | or array. Likewise, C<decode> will croak if given something that is not a |
458 | or array. Likewise, C<decode> will croak if given something that is not a |
444 | JSON object or array. |
459 | JSON object or array. |
445 | |
460 | |
446 | Example, encode a Perl scalar as JSON value with enabled C<allow_nonref>, |
461 | Example, encode a Perl scalar as JSON value without enabled C<allow_nonref>, |
447 | resulting in an invalid JSON text: |
462 | resulting in an error: |
448 | |
463 | |
449 | JSON::XS->new->allow_nonref->encode ("Hello, World!") |
464 | JSON::XS->new->allow_nonref (0)->encode ("Hello, World!") |
450 | => "Hello, World!" |
465 | => hash- or arrayref expected... |
451 | |
466 | |
452 | =item $json = $json->allow_unknown ([$enable]) |
467 | =item $json = $json->allow_unknown ([$enable]) |
453 | |
468 | |
454 | =item $enabled = $json->get_allow_unknown |
469 | =item $enabled = $json->get_allow_unknown |
455 | |
470 | |
… | |
… | |
505 | |
520 | |
506 | This setting has no effect on C<decode>. |
521 | This setting has no effect on C<decode>. |
507 | |
522 | |
508 | =item $json = $json->allow_tags ([$enable]) |
523 | =item $json = $json->allow_tags ([$enable]) |
509 | |
524 | |
510 | =item $enabled = $json->allow_tags |
525 | =item $enabled = $json->get_allow_tags |
511 | |
526 | |
512 | See L<OBJECT SERIALISATION> for details. |
527 | See L<OBJECT SERIALISATION> for details. |
513 | |
528 | |
514 | If C<$enable> is true (or missing), then C<encode>, upon encountering a |
529 | If C<$enable> is true (or missing), then C<encode>, upon encountering a |
515 | blessed object, will check for the availability of the C<FREEZE> method on |
530 | blessed object, will check for the availability of the C<FREEZE> method on |
… | |
… | |
524 | in C<decode>, as if tags were not part of the grammar. |
539 | in C<decode>, as if tags were not part of the grammar. |
525 | |
540 | |
526 | =item $json = $json->filter_json_object ([$coderef->($hashref)]) |
541 | =item $json = $json->filter_json_object ([$coderef->($hashref)]) |
527 | |
542 | |
528 | When C<$coderef> is specified, it will be called from C<decode> each |
543 | When C<$coderef> is specified, it will be called from C<decode> each |
529 | time it decodes a JSON object. The only argument is a reference to the |
544 | time it decodes a JSON object. The only argument is a reference to |
530 | newly-created hash. If the code references returns a single scalar (which |
545 | the newly-created hash. If the code reference returns a single scalar |
531 | need not be a reference), this value (i.e. a copy of that scalar to avoid |
546 | (which need not be a reference), this value (or rather a copy of it) is |
532 | aliasing) is inserted into the deserialised data structure. If it returns |
547 | inserted into the deserialised data structure. If it returns an empty |
533 | an empty list (NOTE: I<not> C<undef>, which is a valid scalar), the |
548 | list (NOTE: I<not> C<undef>, which is a valid scalar), the original |
534 | original deserialised hash will be inserted. This setting can slow down |
549 | deserialised hash will be inserted. This setting can slow down decoding |
535 | decoding considerably. |
550 | considerably. |
536 | |
551 | |
537 | When C<$coderef> is omitted or undefined, any existing callback will |
552 | When C<$coderef> is omitted or undefined, any existing callback will |
538 | be removed and C<decode> will not change the deserialised hash in any |
553 | be removed and C<decode> will not change the deserialised hash in any |
539 | way. |
554 | way. |
540 | |
555 | |
… | |
… | |
687 | |
702 | |
688 | This is useful if your JSON texts are not delimited by an outer protocol |
703 | This is useful if your JSON texts are not delimited by an outer protocol |
689 | and you need to know where the JSON text ends. |
704 | and you need to know where the JSON text ends. |
690 | |
705 | |
691 | JSON::XS->new->decode_prefix ("[1] the tail") |
706 | JSON::XS->new->decode_prefix ("[1] the tail") |
692 | => ([], 3) |
707 | => ([1], 3) |
693 | |
708 | |
694 | =back |
709 | =back |
695 | |
710 | |
696 | |
711 | |
697 | =head1 INCREMENTAL PARSING |
712 | =head1 INCREMENTAL PARSING |
… | |
… | |
738 | C<incr_skip> to skip the erroneous part). This is the most common way of |
753 | C<incr_skip> to skip the erroneous part). This is the most common way of |
739 | using the method. |
754 | using the method. |
740 | |
755 | |
741 | And finally, in list context, it will try to extract as many objects |
756 | And finally, in list context, it will try to extract as many objects |
742 | from the stream as it can find and return them, or the empty list |
757 | from the stream as it can find and return them, or the empty list |
743 | otherwise. For this to work, there must be no separators between the JSON |
758 | otherwise. For this to work, there must be no separators (other than |
744 | objects or arrays, instead they must be concatenated back-to-back. If |
759 | whitespace) between the JSON objects or arrays, instead they must be |
745 | an error occurs, an exception will be raised as in the scalar context |
760 | concatenated back-to-back. If an error occurs, an exception will be |
746 | case. Note that in this case, any previously-parsed JSON texts will be |
761 | raised as in the scalar context case. Note that in this case, any |
747 | lost. |
762 | previously-parsed JSON texts will be lost. |
748 | |
763 | |
749 | Example: Parse some JSON arrays/objects in a given string and return |
764 | Example: Parse some JSON arrays/objects in a given string and return |
750 | them. |
765 | them. |
751 | |
766 | |
752 | my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]"); |
767 | my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]"); |
… | |
… | |
758 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
773 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
759 | all other circumstances you must not call this function (I mean it. |
774 | all other circumstances you must not call this function (I mean it. |
760 | although in simple tests it might actually work, it I<will> fail under |
775 | although in simple tests it might actually work, it I<will> fail under |
761 | real world conditions). As a special exception, you can also call this |
776 | real world conditions). As a special exception, you can also call this |
762 | method before having parsed anything. |
777 | method before having parsed anything. |
|
|
778 | |
|
|
779 | That means you can only use this function to look at or manipulate text |
|
|
780 | before or after complete JSON objects, not while the parser is in the |
|
|
781 | middle of parsing a JSON object. |
763 | |
782 | |
764 | This function is useful in two cases: a) finding the trailing text after a |
783 | This function is useful in two cases: a) finding the trailing text after a |
765 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
784 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
766 | (such as commas). |
785 | (such as commas). |
767 | |
786 | |
… | |
… | |
1275 | expect your input strings to be encoded as UTF-8, that is, no "character" |
1294 | expect your input strings to be encoded as UTF-8, that is, no "character" |
1276 | of the input string must have any value > 255, as UTF-8 does not allow |
1295 | of the input string must have any value > 255, as UTF-8 does not allow |
1277 | that. |
1296 | that. |
1278 | |
1297 | |
1279 | The C<utf8> flag therefore switches between two modes: disabled means you |
1298 | The C<utf8> flag therefore switches between two modes: disabled means you |
1280 | will get a Unicode string in Perl, enabled means you get an UTF-8 encoded |
1299 | will get a Unicode string in Perl, enabled means you get a UTF-8 encoded |
1281 | octet/binary string in Perl. |
1300 | octet/binary string in Perl. |
1282 | |
1301 | |
1283 | =item C<latin1> or C<ascii> flags enabled |
1302 | =item C<latin1> or C<ascii> flags enabled |
1284 | |
1303 | |
1285 | With C<latin1> (or C<ascii>) enabled, C<encode> will escape characters |
1304 | With C<latin1> (or C<ascii>) enabled, C<encode> will escape characters |
… | |
… | |
1553 | are browser design bugs, but it is still you who will have to deal with |
1572 | are browser design bugs, but it is still you who will have to deal with |
1554 | it, as major browser developers care only for features, not about getting |
1573 | it, as major browser developers care only for features, not about getting |
1555 | security right). |
1574 | security right). |
1556 | |
1575 | |
1557 | |
1576 | |
|
|
1577 | =head2 "OLD" VS. "NEW" JSON (RFC 4627 VS. RFC 7159) |
|
|
1578 | |
|
|
1579 | JSON originally required JSON texts to represent an array or object - |
|
|
1580 | scalar values were explicitly not allowed. This has changed, and versions |
|
|
1581 | of JSON::XS beginning with C<4.0> reflect this by allowing scalar values |
|
|
1582 | by default. |
|
|
1583 | |
|
|
1584 | One reason why one might not want this is that this removes a fundamental |
|
|
1585 | property of JSON texts, namely that they are self-delimited and |
|
|
1586 | self-contained, or in other words, you could take any number of "old" |
|
|
1587 | JSON texts and paste them together, and the result would be unambiguously |
|
|
1588 | parseable: |
|
|
1589 | |
|
|
1590 | [1,3]{"k":5}[][null] # four JSON texts, without doubt |
|
|
1591 | |
|
|
1592 | By allowing scalars, this property is lost: in the following example, is |
|
|
1593 | this one JSON text (the number 12) or two JSON texts (the numbers 1 and |
|
|
1594 | 2): |
|
|
1595 | |
|
|
1596 | 12 # could be 12, or 1 and 2 |
|
|
1597 | |
|
|
1598 | Another lost property of "old" JSON is that no lookahead is required to |
|
|
1599 | know the end of a JSON text, i.e. the JSON text definitely ended at the |
|
|
1600 | last C<]> or C<}> character, there was no need to read extra characters. |
|
|
1601 | |
|
|
1602 | For example, a viable network protocol with "old" JSON was to simply |
|
|
1603 | exchange JSON texts without delimiter. For "new" JSON, you have to use a |
|
|
1604 | suitable delimiter (such as a newline) after every JSON text or ensure you |
|
|
1605 | never encode/decode scalar values. |
|
|
1606 | |
|
|
1607 | Most protocols do work by only transferring arrays or objects, and the |
|
|
1608 | easiest way to avoid problems with the "new" JSON definition is to |
|
|
1609 | explicitly disallow scalar values in your encoder and decoder: |
|
|
1610 | |
|
|
1611 | $json_coder = JSON::XS->new->allow_nonref (0) |
|
|
1612 | |
|
|
1613 | This is a somewhat unhappy situation, and the blame can fully be put on |
|
|
1614 | JSON's inmventor, Douglas Crockford, who unilaterally changed the format |
|
|
1615 | in 2006 without consulting the IETF, forcing the IETF to either fork the |
|
|
1616 | format or go with it (as I was told, the IETF wasn't amused). |
|
|
1617 | |
|
|
1618 | |
1558 | =head1 INTEROPERABILITY WITH OTHER MODULES |
1619 | =head1 INTEROPERABILITY WITH OTHER MODULES |
1559 | |
1620 | |
1560 | C<JSON::XS> uses the L<Types::Serialiser> module to provide boolean |
1621 | C<JSON::XS> uses the L<Types::Serialiser> module to provide boolean |
1561 | constants. That means that the JSON true and false values will be |
1622 | constants. That means that the JSON true and false values will be |
1562 | comaptible to true and false values of iother modules that do the same, |
1623 | comaptible to true and false values of other modules that do the same, |
1563 | such as L<JSON::PP> and L<CBOR::XS>. |
1624 | such as L<JSON::PP> and L<CBOR::XS>. |
1564 | |
1625 | |
1565 | |
1626 | |
1566 | =head1 INTEROPERABILITY WITH OTHER JSON DECODERS |
1627 | =head1 INTEROPERABILITY WITH OTHER JSON DECODERS |
1567 | |
1628 | |
… | |
… | |
1584 | |
1645 | |
1585 | When you use C<allow_tags> to use the extended (and also nonstandard and |
1646 | When you use C<allow_tags> to use the extended (and also nonstandard and |
1586 | invalid) JSON syntax for serialised objects, and you still want to decode |
1647 | invalid) JSON syntax for serialised objects, and you still want to decode |
1587 | the generated When you want to serialise objects, you can run a regex |
1648 | the generated When you want to serialise objects, you can run a regex |
1588 | to replace the tagged syntax by standard JSON arrays (it only works for |
1649 | to replace the tagged syntax by standard JSON arrays (it only works for |
1589 | "normal" packagesnames without comma, newlines or single colons). First, |
1650 | "normal" package names without comma, newlines or single colons). First, |
1590 | the readable Perl version: |
1651 | the readable Perl version: |
1591 | |
1652 | |
1592 | # if your FREEZE methods return no values, you need this replace first: |
1653 | # if your FREEZE methods return no values, you need this replace first: |
1593 | $json =~ s/\( \s* (" (?: [^\\":,]+|\\.|::)* ") \s* \) \s* \[\s*\]/[$1]/gx; |
1654 | $json =~ s/\( \s* (" (?: [^\\":,]+|\\.|::)* ") \s* \) \s* \[\s*\]/[$1]/gx; |
1594 | |
1655 | |
… | |
… | |
1612 | |
1673 | |
1613 | And after decoding the JSON text, you could walk the data |
1674 | And after decoding the JSON text, you could walk the data |
1614 | structure looking for arrays with a first element of |
1675 | structure looking for arrays with a first element of |
1615 | C<XU1peReLzT4ggEllLanBYq4G9VzliwKF>. |
1676 | C<XU1peReLzT4ggEllLanBYq4G9VzliwKF>. |
1616 | |
1677 | |
1617 | The same approach cna be used to create the tagged format with another |
1678 | The same approach can be used to create the tagged format with another |
1618 | encoder. First, you create an array with the magic string as first member, |
1679 | encoder. First, you create an array with the magic string as first member, |
1619 | the classname as second, and constructor arguments last, encode it as part |
1680 | the classname as second, and constructor arguments last, encode it as part |
1620 | of your JSON structure, and then: |
1681 | of your JSON structure, and then: |
1621 | |
1682 | |
1622 | $json =~ s/\[\s*"XU1peReLzT4ggEllLanBYq4G9VzliwKF"\s*,\s*("([^\\":,]+|\\.|::)*")\s*,/($1)[/g; |
1683 | $json =~ s/\[\s*"XU1peReLzT4ggEllLanBYq4G9VzliwKF"\s*,\s*("([^\\":,]+|\\.|::)*")\s*,/($1)[/g; |
1623 | |
1684 | |
1624 | Again, this has some limitations - the magic string must not be encoded |
1685 | Again, this has some limitations - the magic string must not be encoded |
1625 | with character escapes, and the constructor arguments must be non-empty. |
1686 | with character escapes, and the constructor arguments must be non-empty. |
1626 | |
1687 | |
1627 | |
1688 | |
1628 | =head1 RFC7158 |
1689 | =head1 RFC7159 |
1629 | |
1690 | |
1630 | Since this module was written, Google has written a new JSON RFC, RFC |
1691 | Since this module was written, Google has written a new JSON RFC, RFC 7159 |
1631 | 7158. Unfortunately, this RFC breaks compatibility with both the original |
1692 | (and RFC7158). Unfortunately, this RFC breaks compatibility with both the |
1632 | JSON specification on www.json.org and RFC4627. |
1693 | original JSON specification on www.json.org and RFC4627. |
1633 | |
1694 | |
1634 | As far as I can see, you can get partial compatibility when parsing by |
1695 | As far as I can see, you can get partial compatibility when parsing by |
1635 | using C<< ->allow_nonref >>. However, consider thew security implications |
1696 | using C<< ->allow_nonref >>. However, consider the security implications |
1636 | of doing so. |
1697 | of doing so. |
1637 | |
1698 | |
1638 | I haven't decided yet whether to break compatibility with RFC4627 by |
1699 | I haven't decided yet when to break compatibility with RFC4627 by default |
1639 | default (and potentially leave applications insecure), or change the |
1700 | (and potentially leave applications insecure) and change the default to |
1640 | default to follow RFC7158. |
1701 | follow RFC7159, but application authors are well advised to call C<< |
|
|
1702 | ->allow_nonref(0) >> even if this is the current default, if they cannot |
|
|
1703 | handle non-reference values, in preparation for the day when the default |
|
|
1704 | will change. |
1641 | |
1705 | |
1642 | |
1706 | |
1643 | =head1 THREADS |
1707 | =head1 (I-)THREADS |
1644 | |
1708 | |
1645 | This module is I<not> guaranteed to be thread safe and there are no |
1709 | This module is I<not> guaranteed to be ithread (or MULTIPLICITY-) safe |
1646 | plans to change this until Perl gets thread support (as opposed to the |
1710 | and there are no plans to change this. Note that perl's builtin so-called |
1647 | horribly slow so-called "threads" which are simply slow and bloated |
1711 | threads/ithreads are officially deprecated and should not be used. |
1648 | process simulations - use fork, it's I<much> faster, cheaper, better). |
|
|
1649 | |
|
|
1650 | (It might actually work, but you have been warned). |
|
|
1651 | |
1712 | |
1652 | |
1713 | |
1653 | =head1 THE PERILS OF SETLOCALE |
1714 | =head1 THE PERILS OF SETLOCALE |
1654 | |
1715 | |
1655 | Sometimes people avoid the Perl locale support and directly call the |
1716 | Sometimes people avoid the Perl locale support and directly call the |