aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/ext_depends/D-YAML/docs/articles/spec_differences.md
diff options
context:
space:
mode:
authorRalph Amissah <ralph.amissah@gmail.com>2021-02-19 17:10:51 -0500
committerRalph Amissah <ralph.amissah@gmail.com>2021-02-24 16:46:47 -0500
commit02ca32ae0a5bc290918d2b2a3288e385b9cc6b11 (patch)
tree06379785e8a0165a7deb981c2eba362894820634 /src/ext_depends/D-YAML/docs/articles/spec_differences.md
parentbuild from static source-tree pre fetch depends (diff)
external & build dependences in src tree
- external & build dependences boost licensed - ext_depends (external depends) - D-YAML - tinyendian - d2sqlite3 - imageformats - build_depends - dub2nix
Diffstat (limited to 'src/ext_depends/D-YAML/docs/articles/spec_differences.md')
-rw-r--r--src/ext_depends/D-YAML/docs/articles/spec_differences.md64
1 files changed, 64 insertions, 0 deletions
diff --git a/src/ext_depends/D-YAML/docs/articles/spec_differences.md b/src/ext_depends/D-YAML/docs/articles/spec_differences.md
new file mode 100644
index 0000000..93cf038
--- /dev/null
+++ b/src/ext_depends/D-YAML/docs/articles/spec_differences.md
@@ -0,0 +1,64 @@
+# Differences between D:YAML and the YAML specification
+
+There are some differences between D:YAML and the YAML 1.1
+specification. Some are caused by difficulty of implementation of some
+features, such as multiple Unicode encodings within single stream, and
+some by unnecessary restrictions or ambiguities in the specification.
+
+Still, D:YAML tries to be as close to the specification as possible. It
+should never load documents with different meaning than according to the
+specification, and documents that fail to load should be very rare (for
+instance, very few files use multiple Unicode encodings).
+
+## List of known differences:
+
+Differences that can cause valid YAML documents not to load:
+
+ - No support for byte order marks and multiple Unicode encodings in a
+ stream.
+
+ - Plain scalars in flow context cannot contain `,`, `:` and `?`. This
+ might change with `:` in the future. See
+ <http://pyyaml.org/wiki/YAMLColonInFlowContext> for details.
+
+ - The specification does not restrict characters for anchors and
+ aliases. This may lead to problems, for instance, the document:
+
+ [ *alias, value ]
+
+ can be interpteted in two ways, as:
+
+ [ "value" ]
+
+ and:
+
+ [ *alias , "value" ]
+
+ Therefore we restrict aliases and anchors to ASCII alphanumeric
+ characters.
+
+ - The specification is confusing about tabs in plain scalars. We don't
+ use tabs in plain scalars at all.
+
+ - There is no support for recursive data structures in DYAML.
+
+Other differences:
+
+ - Indentation is ignored in the flow context, which is less
+ restrictive than the specification. This allows code such as:
+
+ key: {
+ }
+
+ - Indentation rules for quoted scalars are loosed: They don't need to
+ adhere indentation as `"` and `'` clearly mark the beginning and the
+ end of them.
+
+ - We allow `_` in tag handles.
+
+ - Right now, two mappings with the same contents but different
+ orderings are considered unequal, even if they are unordered
+ mappings. This is because all mappings are ordered in the D:YAML
+ implementation. This should change in future, once D associative
+ arrays work with variant types or a map class or struct appears in
+ Phobos.