On Fri, 2008-01-18 at 17:22 -0600, Jonathan Rockway wrote: > On Fri, 2008-01-18 at 16:57 -0600, Ian Malpass wrote: > > I got a failure message from CPAN testers for Pod::Extract::URI for > > 5.11.0 patch 33001 on Linux 2.6.22-3-amd64 (x86_64-linux-thread-multi-ld)[0] > > > > The failures were where I was testing to see if an arrayref of qr// > > patterns was the array I was expecting. is_deeply() has heretofore > > worked perfectly well. > > > > The test line in question is: > > > > is_deeply( $peu->stop_uris, [ qr/foo/ ] ); > > > > And the failure is: > > > > # Failed test at t/new.t line 42. > > # Structures begin differing at: > > # $got->[0] = (?i-xsm:foo) > > # $expected->[0] = (?-xism:foo) > > # Looks like you failed 1 test of 24. > > Are you positive you didn't mean to say qr/foo/i ? Are you sure that > $peu->stop_uris should be returning qr/foo/i instead of qr/foo/?
Sorry to reply to myself (it's Friday, what can I say)... but under 5.8.8 and 5.10.0, this test passes: is_deeply qr/foo/i, qr/foo/ # pass Honestly, I think it's a bug in the older versions and 5.11.0 gets it right. Those two regexes aren't the same. Since there's been some discussion on p5p about regex object internals, I'll forward the message over there so they know the behavior has changed. Regards, Jonathan Rockway
signature.asc
Description: This is a digitally signed message part
