… | |
… | |
922 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
922 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
923 | lengths that JSON doesn't have and also has different and incompatible |
923 | lengths that JSON doesn't have and also has different and incompatible |
924 | unicode handling, so you should make sure that your hash keys are |
924 | unicode handling, so you should make sure that your hash keys are |
925 | noticeably shorter than the 1024 "stream characters" YAML allows and that |
925 | noticeably shorter than the 1024 "stream characters" YAML allows and that |
926 | you do not have codepoints with values outside the Unicode BMP (basic |
926 | you do not have codepoints with values outside the Unicode BMP (basic |
927 | multilingual page). |
927 | multilingual page). YAML also does not allow C<\/> sequences in strings |
|
|
928 | (which JSON::XS does not I<currently> generate). |
928 | |
929 | |
929 | There might be other incompatibilities that I am not aware of. In general |
930 | There might be other incompatibilities that I am not aware of. In general |
930 | you should not try to generate YAML with a JSON generator or vice versa, |
931 | you should not try to generate YAML with a JSON generator or vice versa, |
931 | or try to parse JSON with a YAML parser or vice versa: chances are high |
932 | or try to parse JSON with a YAML parser or vice versa: chances are high |
932 | that you will run into severe interoperability problems when you least |
933 | that you will run into severe interoperability problems when you least |