On Mon Jun 18 19:03:09 2007, DMUEY wrote:
Show quoted text> Apparently it tied hashes period:
>
> Tied hashes make YAML::Syck puke...
>
> root@c5release-2 [~]# perl -Mstrict -wle 'use YAML::Syck;my $ref = {
> "howdy" => { a =>
> 1 } };print YAML::Syck::Dump( $ref );'
> ---
> howdy:
> a: 1
>
> root@c5release-2 [~]#
>
> root@c5release-2 [~]# perl -Mstrict -wle 'use YAML::Syck;use
> Tie::IxHash;tie( my %tied,
> "Tie::IxHash" );%tied = ("howdy" => { a => 1 } );print
> YAML::Syck::Dump( \%tied );'
> --- {}
Can you two check if this is due to the hash iterator bugs reported in
#34166 and #54167?
Also, have a form reply:
(This is a form-reply that isn't specific to your particular report)
YAML::Syck has just acquired one new maintainer (me), it still doesn't
have anyone that *cares* about it. But I'm willing to help solve your
report & release a new version with the fix if it's easy for me.
It now has a Git repository at:
http://github.com/avar/YAML-Syck
If your report is a patch that fixes a problem, great. Please remake
the patch against Git by forking that repo and sending me a pull
request on GitHub (or an update to this bug if you prefer
git-format-patch(1) or some other repo provider..). Make sure to
include a test for what you fixed.
If your report is some code that fails (and you have a testcase for
it) a patch against the test suite to demonstrate that failure would
be very useful. It's OK if the test crashes and burns, see
Test::More's docs for how to make TODO tests that fail now, but
shouldn't. Even if it segfaults perl C<system $^X => qw/ -Mblib
-MYAML::Syck .../> or something like that and checking the return
value will do.
