| … | |
… | |
| 906 | |
906 | |
| 907 | |
907 | |
| 908 | =head2 JSON and YAML |
908 | =head2 JSON and YAML |
| 909 | |
909 | |
| 910 | You often hear that JSON is a subset of YAML. This is, however, a mass |
910 | You often hear that JSON is a subset of YAML. This is, however, a mass |
| 911 | hysteria and very far from the truth. In general, there is no way to |
911 | hysteria(*) and very far from the truth. In general, there is no way to |
| 912 | configure JSON::XS to output a data structure as valid YAML that works for |
912 | configure JSON::XS to output a data structure as valid YAML that works for |
| 913 | all cases. |
913 | all cases. |
| 914 | |
914 | |
| 915 | If you really must use JSON::XS to generate YAML, you should use this |
915 | If you really must use JSON::XS to generate YAML, you should use this |
| 916 | algorithm (subject to change in future versions): |
916 | algorithm (subject to change in future versions): |
| … | |
… | |
| 930 | 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 |
| 931 | 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, |
| 932 | 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 |
| 933 | that you will run into severe interoperability problems when you least |
933 | that you will run into severe interoperability problems when you least |
| 934 | expect it. |
934 | expect it. |
|
|
935 | |
|
|
936 | =over 4 |
|
|
937 | |
|
|
938 | =item (*) |
|
|
939 | |
|
|
940 | This is spread actively by the YAML team, however. For many years now they |
|
|
941 | claim YAML were a superset of JSON, even when proven otherwise. |
|
|
942 | |
|
|
943 | Even the author of this manpage was at some point accused of providing |
|
|
944 | "incorrect" information, despite the evidence presented (claims ranged |
|
|
945 | from "your documentation contains inaccurate and negative statements about |
|
|
946 | YAML" (the only negative comment is this footnote, and it didn't exist |
|
|
947 | back then; the question on which claims were inaccurate was never answered |
|
|
948 | etc.) to "the YAML spec is not up-to-date" (the *real* and suppsedly |
|
|
949 | JSON-compatible spec is apparently not currently publicly available) |
|
|
950 | to actual requests to replace this section by *incorrect* information, |
|
|
951 | suppressing information about the real problem). |
|
|
952 | |
|
|
953 | So whenever you are told that YAML was a superset of JSON, first check |
|
|
954 | wether it is really true (it might be when you check it, but it cetrainly |
|
|
955 | is not true when this was written). I would much prefer if the YAML team |
|
|
956 | would spent their time on actually making JSON compatibility a truth |
|
|
957 | (JSON, after all, has a very small and simple specification) instead of |
|
|
958 | trying to lobby/force people into reporting untruths. |
|
|
959 | |
|
|
960 | =back |
| 935 | |
961 | |
| 936 | |
962 | |
| 937 | =head2 SPEED |
963 | =head2 SPEED |
| 938 | |
964 | |
| 939 | It seems that JSON::XS is surprisingly fast, as shown in the following |
965 | It seems that JSON::XS is surprisingly fast, as shown in the following |
