Skip Menu |
 

This queue is for tickets about the YAML-Syck CPAN distribution.

Report information
The Basics
Id: 26182
Status: resolved
Priority: 0/
Queue: YAML-Syck

People
Owner: Nobody in particular
Requestors: fred [...] thomascorner.com
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 1.10
Fixed in: (no value)



MIME-Version: 1.0 (Apple Message framework v752.2)
X-Spam-Status: No, hits=-2.6 required=8.0 tests=BAYES_00,DK_POLICY_SIGNSOME
X-Mailer: Apple Mail (2.752.2)
Received-SPF: neutral (x1.develooper.com: local policy)
content-type: text/plain; charset="utf-8"; format="flowed"
Received: from la.mx.develooper.com (x1.develooper.com [63.251.223.170]) by diesel.bestpractical.com (Postfix) with SMTP id 5C3914D8005 for <bug-YAML-Syck [...] rt.cpan.org>; Sun, 8 Apr 2007 19:34:48 -0400 (EDT)
Received: (qmail 3455 invoked by alias); 8 Apr 2007 23:34:47 -0000
Received: from tr11.bluewin.ch (HELO tr11.bluewin.ch) (195.186.18.81) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Apr 2007 16:34:45 -0700
Received: from [192.168.1.3] (62.203.12.229) by tr11.bluewin.ch (Bluewin 7.3.121) id 45F5126D0025105D for bug-YAML-Syck [...] rt.cpan.org; Sun, 8 Apr 2007 23:34:39 +0000
Delivered-To: cpan-bug+yaml-syck [...] diesel.bestpractical.com
Subject: Incompatible with Tie::LLHash
Return-Path: <fred [...] thomascorner.com>
X-Original-To: bug-YAML-Syck [...] rt.cpan.org
X-Spam-Check-BY: la.mx.develooper.com
Date: Mon, 9 Apr 2007 01:34:40 +0200
Message-Id: <0E21ACEB-9326-47D2-A53F-BC54A6A9DB04 [...] thomascorner.com>
To: bug-YAML-Syck [...] rt.cpan.org
Content-Transfer-Encoding: 7bit
From: Frédéric Thomas <fred [...] thomascorner.com>
X-RT-Original-Encoding: US-ASCII
Content-Length: 335
Download (untitled) / with headers
text/plain 335b
YAML::Syck 0.84, Perl 5.8.8, OS X 10.4.9 (also seen with previous versions of all the above) ----- use JSON::Syck; use Tie::LLHash; tie (my %resultHash, "Tie::LLHash", {lazy => 1}); $resultHash{'hello'} = 1; $resultHash{'helli'} = 2; my $json = JSON::Syck::Dump(\%resultHash); print($json . "\n"); ----- => prints {} Thanks Fred
MIME-Version: 1.0
Subject: Incompatible with Tied hashes
In-Reply-To: <0E21ACEB-9326-47D2-A53F-BC54A6A9DB04 [...] thomascorner.com>
X-Mailer: MIME-tools 5.418 (Entity 5.418)
Content-Disposition: inline
References: <0E21ACEB-9326-47D2-A53F-BC54A6A9DB04 [...] thomascorner.com>
Message-Id: <rt-3.6.HEAD-4752-1182207770-921.26182-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf8"
Content-Transfer-Encoding: binary
From: DMUEY [...] cpan.org
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
Content-Length: 448
Download (untitled) / with headers
text/plain 448b
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 );' --- {} root@c5release-2 [~]#
MIME-Version: 1.0
In-Reply-To: <rt-3.6.HEAD-4752-1182207770-921.26182-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
References: <0E21ACEB-9326-47D2-A53F-BC54A6A9DB04 [...] thomascorner.com> <rt-3.6.HEAD-4752-1182207770-921.26182-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.HEAD-6784-1274355144-1898.26182-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 1663
Download (untitled) / with headers
text/plain 1.6k
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.
MIME-Version: 1.0
In-Reply-To: <rt-3.8.HEAD-6784-1274355144-1898.26182-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
References: <0E21ACEB-9326-47D2-A53F-BC54A6A9DB04 [...] thomascorner.com> <rt-3.6.HEAD-4752-1182207770-921.26182-0-0 [...] rt.cpan.org> <rt-3.8.HEAD-6784-1274355144-1898.26182-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.HEAD-2370-1279221804-1915.26182-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 601
Download (untitled) / with headers
text/plain 601b
Show quoted text
> Can you two check if this is due to the hash iterator bugs reported in > #34166 and #54167?
34166 is labeled as a dupe of 54167 54167 is reported to be committed into 1.09 That said... I don't think it fixes things: # NOT TIED $>perl -Mstrict -wlE 'use YAML::Syck;say $YAML::Syck::VERSION; my $ref = { "howdy" => { a =>1 } };print YAML::Syck::Dump( $ref );' 1.10 --- howdy: a: 1 # TIED STILL BROKEN $>perl -Mstrict -wlE 'use YAML::Syck;say $YAML::Syck::VERSION; use Tie::IxHash;tie( my %tied,"Tie::IxHash" );%tied = ("howdy" => { a => 1 } );print YAML::Syck::Dump( \%tied );' 1.10 --- {}
MIME-Version: 1.0
In-Reply-To: <rt-3.8.HEAD-2370-1279221804-1915.26182-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
References: <0E21ACEB-9326-47D2-A53F-BC54A6A9DB04 [...] thomascorner.com> <rt-3.6.HEAD-4752-1182207770-921.26182-0-0 [...] rt.cpan.org> <rt-3.8.HEAD-6784-1274355144-1898.26182-0-0 [...] rt.cpan.org> <rt-3.8.HEAD-2370-1279221804-1915.26182-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.HEAD-2366-1279575422-1082.26182-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
RT-Send-CC: DMUEY [...] cpan.org
Content-Length: 182
Download (untitled) / with headers
text/plain 182b
All tied variables do not work. I have updated t/yaml-tie.t to show where all ties fall over. This would be a significant change to the source to support walking a tied variable.
X-RT-Interface: REST
MIME-Version: 1.0
X-Mailer: MIME-tools 5.504 (Entity 5.504)
RT-Message-ID: <rt-4.0.18-11674-1494492991-956.26182-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
Content-Length: 73
Ticket migrated to github as https://github.com/toddr/YAML-Syck/issues/34


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.