| … | |
… | |
| 36 | JSON::XS are installed, then JSON will fall back on JSON::XS (this can |
36 | JSON::XS are installed, then JSON will fall back on JSON::XS (this can |
| 37 | be overridden) with no overhead due to emulation (by inheriting |
37 | be overridden) with no overhead due to emulation (by inheriting |
| 38 | constructor and methods). If JSON::XS is not available, it will fall |
38 | constructor and methods). If JSON::XS is not available, it will fall |
| 39 | back to the compatible JSON::PP module as backend, so using JSON instead |
39 | back to the compatible JSON::PP module as backend, so using JSON instead |
| 40 | of JSON::XS gives you a portable JSON API that can be fast when you need |
40 | of JSON::XS gives you a portable JSON API that can be fast when you need |
| 41 | and doesn't require a C compiler when that is a problem. |
41 | it and doesn't require a C compiler when that is a problem. |
| 42 | |
42 | |
| 43 | As this is the n-th-something JSON module on CPAN, what was the reason |
43 | As this is the n-th-something JSON module on CPAN, what was the reason |
| 44 | to write yet another JSON module? While it seems there are many JSON |
44 | to write yet another JSON module? While it seems there are many JSON |
| 45 | modules, none of them correctly handle all corner cases, and in most |
45 | modules, none of them correctly handle all corner cases, and in most |
| 46 | cases their maintainers are unresponsive, gone missing, or not listening |
46 | cases their maintainers are unresponsive, gone missing, or not listening |
| … | |
… | |
| 1563 | default to follow RFC7159, but application authors are well advised to |
1563 | default to follow RFC7159, but application authors are well advised to |
| 1564 | call "->allow_nonref(0)" even if this is the current default, if they |
1564 | call "->allow_nonref(0)" even if this is the current default, if they |
| 1565 | cannot handle non-reference values, in preparation for the day when the |
1565 | cannot handle non-reference values, in preparation for the day when the |
| 1566 | default will change. |
1566 | default will change. |
| 1567 | |
1567 | |
| 1568 | THREADS |
1568 | (I-)THREADS |
| 1569 | This module is *not* guaranteed to be thread safe and there are no plans |
1569 | This module is *not* guaranteed to be ithread (or MULTIPLICITY-) safe |
| 1570 | to change this until Perl gets thread support (as opposed to the |
1570 | and there are no plans to change this. Note that perl's builtin |
| 1571 | horribly slow so-called "threads" which are simply slow and bloated |
1571 | so-called theeads/ithreads are officially deprecated and should not be |
| 1572 | process simulations - use fork, it's *much* faster, cheaper, better). |
1572 | used. |
| 1573 | |
|
|
| 1574 | (It might actually work, but you have been warned). |
|
|
| 1575 | |
1573 | |
| 1576 | THE PERILS OF SETLOCALE |
1574 | THE PERILS OF SETLOCALE |
| 1577 | Sometimes people avoid the Perl locale support and directly call the |
1575 | Sometimes people avoid the Perl locale support and directly call the |
| 1578 | system's setlocale function with "LC_ALL". |
1576 | system's setlocale function with "LC_ALL". |
| 1579 | |
1577 | |
