You made me curious, especially since here at work I'm investigating the possibility of using YAML to serialize some data. So I installed YAML::Syck and tried it on the same data as the OP:

$ perl -MYAML::Syck -le 'print Dump { zip => "07102" }'
---
zip: 07102
[download]

So the behaviour is just the same. But I also get

$ perl -MData::Dumper -MYAML::Syck -le 'print Dumper Load Dump { zip =
+> "07102" }'
$VAR1 = {
          'zip' => '07102'
        };
[download]

which is not what he fears. That only happens if $YAML::Syck::ImplicitTyping is set to a true value (by default, it's false):

$ perl -MData::Dumper -MYAML::Syck -le '$YAML::Syck::ImplicitTyping=1;
print Dumper Load Dump { zip => "07102" }'
$VAR1 = {
          'zip' => 3650
        };
[download]

Hmm... how to write a dependency-installation failure test that goes inside the distribution... if I can figure that out, the recursive nature sounds very Ingy-ish.

# t/yaml_install.t
use Test::Install 'YAML';
[download]

Thanks for your comments.

The spec seems pretty clear that something like:



zip: 07102
[download]

would be implicitly typed as an octal integer. I also tried YAML::Syck, but can't get it to produce a "valid" YAML file that can be read with other parsers which force implicit casting of data types.

- Devnul