PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` YAML::Syck and YAML.pm 0.60 breaks compatibility with older versions by changing the tags that are output for serialized objects. This was the old way: --- !perl/Foo::Bar {} --- !perl/@Baz [] --- !perl/$Quux "" New way: --- !!perl/hash:Foo::Bar {} --- !!perl/array:Baz [] --- !!perl/scalar:Quux "" * This change was made after discussions with the Python and Ruby implementers to standardize on this form. * YAML::Syck was updated at the same time as YAML.pm so that they serialize objects the same way. * YAML.pm roundtrips the new format and still parses the old (now deprecated) format. * The best strategy is to update to the latest version. * There are potential problems if you use YAML for RPC and the server and client versions don't match.