Another YAML bug?

[Vladimir Marteev]

#!/usr/bin/ruby1.8
require 'yaml'
a = { "b" => "c", "d" => nil, "e" => "f" }
puts a.to_yaml

result:

---
b: c
d:
e: f

but must be:

 

[Jacob Fugal]

#!/usr/bin/ruby1.8
require 'yaml'
a = { "b" => "c", "d" => nil, "e" => "f" }
puts a.to_yaml

result:

---
b: c
d:
e: f

but must be:

Not a bug.

According to [1] the canonical representation for !!null is indeed
'~', but the empty string (as well as the tokens 'null', 'Null' and
'NULL') are also acceptable representations. And we needn't worry
about confusion with the empty string since the empty string must be
represented with quotation marks, e.g.:

d: ""

There may be an argument that the YAML serialization of Ruby's nil
*should* be '~' instead of an empty string, but it is not the case
that it *must* be so.

Jacob Fugal

[1] http://yaml.org/type/null.html