Tue Mar 23 09:14:53 2010: Request 55746 was acted upon.
Transaction: Correspondence added by RSCHUPP
Queue: Module-ScanDeps
Subject: hash-as-condition bug in Module::ScanDeps::DataFeed
Broken in: (no value)
Severity: (no value)
Owner: Nobody
Requestors: [email protected]
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=55746 >
On Mon Mar 22 17:28:12 2010, [email protected] wrote:
> In 5.8.2, there is a specific bug in the handling of hash-as-scalar
> for
> tied hashes. The nature of the bug is that the scalarification looks
> at
Ah yes, correct behaviour of "if (%hash) ..." for a tied %hash
came indeed in non-ancient times (can one call early 5.8.x "medieval"?).
Thanks for your analysis - don't get me started on tied hashes:
most XS modules will break when presented with (a reference to)
a tied hash instead of a "real" hash. That's because you
have to use different functions from XS (in certain situations).
I think the conditional was perhaps meant to test for
the existence of %Config::Config (PAR and PAR::Packer sometimes
play games by directly manipulating %INC, so that after
a successful "use Config" you still can't be sure that
Config.pm has actually been loaded). But that's not the way
to test for that.
Anyway, I just committed your patch, will be in the next release.