fork YAML::XS ?

[rurban]

If there will not be any upstream action (waiting since March 2016)

Todo:

• add SafeLoad to be usable for cpan. see python (don't load code nor set objects)
• remove zild/dzil/Spiffy, convert to EUMM, fix Test::Base to be usable (put into inc)

Done:

• fixed remaining hard utf8 errors while reading. see https://github.com/perl11/cperl/issues/161
• fix the many clang and gcc compiler warnings (libyaml, done with 0.73)
• allow CPAN::Meta::YAML/YAML/YAML::Syck/YAML::XS roundtrips
• add two new features: NonStrict mode (for perl5 compat), IndentlessMap=0 (new default)
• Add dumper options Indent, BestWidth, Canonical, Unicode, Encoding, LineBreak, OpenEnded (kept defaults)
• Add loader option NonStrict, Encoding (kept defaults)
• DumpFile,LoadFile is now XS only, and do accept mg pv, io objects and fileglobs. support filename in error messages.
• Use error codes, return undef on error.

See:

• http://blogs.perl.org/users/rurban/2016/03/yaml-patches-done.html
• http://blogs.perl.org/users/rurban/2016/03/more-on-yaml-syck-looks-much-better.html
• and esp. http://blogs.perl.org/users/rurban/2016/03/on-yaml-and-yamlxs-inconsistencies.html

Background: I'm not willing to deal with zild/dzil. This is not a sane build system. The generated zild MANIFEST is broken. Furtheron Spiffy is broken for signatures. The testsuite relies on Spiffy. I made a fixed Spiffy which can deal with sigs.

[rurban]

YAML::Sec maybe. I'll choose YAML::Safe

[rurban]

Started with YAML::Safe for v5.30.0c as the lastest YAML::XS updates made the situation worse than better. See https://github.com/rurban/YAML-Safe