Skip Menu |

This queue is for tickets about the Class-Fields CPAN distribution.

Report information
The Basics
Id: 5293
Status: resolved
Priority: 0/
Queue: Class-Fields

People
Owner: Nobody in particular
Requestors: eamon [...] eamondaly.com
rz10 [...] cornell.edu
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.201
Fixed in: (no value)



Subject: Different warning in perl 5.8.3
Perl 5.8.3 has a slightly different warning for the collision in t/bugs.t. Here's a clumsy patch: # diff --unified t/bugs.t.orig t/bugs.t --- t/bugs.t.orig Wed Feb 11 12:06:07 2004 +++ t/bugs.t Wed Feb 11 12:11:44 2004 @@ -76,9 +76,18 @@ use public qw(f); use base qw(Foo); # base comes after 'use public' - -::ok( $warnings eq <<WARN, 'Improper use of fields & base warned about' ); +my $mesg = <<WARN; Bar is inheriting from Foo but already has its own fields! This will cause problems with pseudo-hashes. Be sure you use base BEFORE declaring fields WARN + +if ($^V gt v5.8.2) { + $mesg = <<WARN; +Bar is inheriting from Foo but already has its own fields! +This will cause problems. +Be sure you use base BEFORE declaring fields +WARN +} + +::ok($warnings eq $mesg, 'Improper use of fields & base warned about' );
To: schwern [...] pobox.com
From: Ray Zimmerman <rz10 [...] cornell.edu>
Subject: bug in Class::Fields t/bugs.t
Date: Tue, 22 Feb 2005 12:19:19 -0500
Under perl-5.8.6 test 3 of t/bugs.t fails for Class-Fields-0.201. It appears that the 2nd line of the warning has changed to "There will cause problems." with no mention of pseudo-hashes. Minor problem, but it requires forcing a normal CPAN install. Ray Zimmerman Director, Laboratory for Experimental Economics and Decision Research 428-B Phillips Hall, Cornell University, Ithaca, NY 14853 phone: (607) 255-9645
From: Ray Zimmerman
Disregard this one since it is the same as bug 5293, which included a patch to fix it. Sorry.
From: Salve J. Nilsen
[ZMAN - Thu Feb 24 08:07:32 2005]: Show quoted text
> Disregard this one since it is the same as bug 5293, which included a > patch to fix it. Sorry.
The bug may very well have a patch/fix, but hasn't shown up on CPAN yet (a year after it was submitted!) Would it be too much to ask for a new release of Class::Fields, even if it only contains this one bugfix?
[guest - Thu Mar 31 03:15:24 2005]: Show quoted text
> The bug may very well have a patch/fix, but hasn't shown up on CPAN > yet > (a year after it was submitted!) Would it be too much to ask for a new > release of Class::Fields, even if it only contains this one bugfix?
I lost my CVS repository in a hard drive failure and haven't gotten around to restoring it from the backup, where "backup" is an old hard drive for which I no longer have a computer to access and which I hope does, in fact, contain a backup. Anyhow, I'm going to give it a shot at restoration soon.
From: bkw [...] cpan.org
On Di. 26. Jul. 2005, 11:18:38, MSCHWERN wrote: Show quoted text
> I lost my CVS repository in a hard drive failure and haven't gotten > around to restoring it from the backup, where "backup" is an old hard > drive for which I no longer have a computer to access and which I hope > does, in fact, contain a backup. > > Anyhow, I'm going to give it a shot at restoration soon.
Here is a patch that tries to fix that problem a little more generic, namely with a regex. This should improve your cpantesters ranking ;-) regards, bkw
--- t/bugs.t.orig 2003-05-28 23:41:16.000000000 +0200 +++ t/bugs.t 2007-02-27 18:14:55.401261433 +0100 @@ -77,8 +77,8 @@ use base qw(Foo); # base comes after 'use public' -::ok( $warnings eq <<WARN, 'Improper use of fields & base warned about' ); +::ok( $warnings =~ <<WARN, 'Improper use of fields & base warned about' ); Bar is inheriting from Foo but already has its own fields! -This will cause problems with pseudo-hashes. +This will cause problems.* Be sure you use base BEFORE declaring fields WARN
Prod. Gentle. Imagine that Class::Fields is a prereq for YAML2. Profit.
Fixed. Will be in the next release.