| … | |
… | |
| 713 | calls). |
713 | calls). |
| 714 | |
714 | |
| 715 | JSON::XS will only attempt to parse the JSON text once it is sure it |
715 | JSON::XS will only attempt to parse the JSON text once it is sure it |
| 716 | has enough text to get a decisive result, using a very simple but |
716 | has enough text to get a decisive result, using a very simple but |
| 717 | truly incremental parser. This means that it sometimes won't stop as |
717 | truly incremental parser. This means that it sometimes won't stop as |
| 718 | early as the full parser, for example, it doesn't detect parenthese |
718 | early as the full parser, for example, it doesn't detect mismatched |
| 719 | mismatches. The only thing it guarantees is that it starts decoding as |
719 | parentheses. The only thing it guarantees is that it starts decoding as |
| 720 | soon as a syntactically valid JSON text has been seen. This means you need |
720 | soon as a syntactically valid JSON text has been seen. This means you need |
| 721 | to set resource limits (e.g. C<max_size>) to ensure the parser will stop |
721 | to set resource limits (e.g. C<max_size>) to ensure the parser will stop |
| 722 | parsing in the presence if syntax errors. |
722 | parsing in the presence if syntax errors. |
| 723 | |
723 | |
| 724 | The following methods implement this incremental parser. |
724 | The following methods implement this incremental parser. |
| … | |
… | |
| 1255 | well - using C<eval> naively simply I<will> cause problems. |
1255 | well - using C<eval> naively simply I<will> cause problems. |
| 1256 | |
1256 | |
| 1257 | Another problem is that some javascript implementations reserve |
1257 | Another problem is that some javascript implementations reserve |
| 1258 | some property names for their own purposes (which probably makes |
1258 | some property names for their own purposes (which probably makes |
| 1259 | them non-ECMAscript-compliant). For example, Iceweasel reserves the |
1259 | them non-ECMAscript-compliant). For example, Iceweasel reserves the |
| 1260 | C<__proto__> property name for it's own purposes. |
1260 | C<__proto__> property name for its own purposes. |
| 1261 | |
1261 | |
| 1262 | If that is a problem, you could parse try to filter the resulting JSON |
1262 | If that is a problem, you could parse try to filter the resulting JSON |
| 1263 | output for these property strings, e.g.: |
1263 | output for these property strings, e.g.: |
| 1264 | |
1264 | |
| 1265 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
1265 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
