Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Perl-Critic CPAN distribution.

Report information
The Basics
Id: 24534
Status: resolved
Priority: 0/
Queue: Perl-Critic

People
Owner: Nobody in particular
Requestors: Jeff.Thalhammer [...] barclaysglobal.com
Cc:
AdminCc:

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



Subject: $foo{local} triggers Variables::RequireInitializationForLocalVars
Date: Tue, 23 Jan 2007 11:52:22 -0800
To: <bug-Perl-Critic [...] rt.cpan.org>
From: "Thalhammer, Jeffrey BGI SF" <Jeff.Thalhammer [...] barclaysglobal.com>
This code: $foo{local} = 42; falsely reports this violation: "local" variable not initialized at line 1, column 6. See page 78 of PBP. (Severity: 3) -- This message and any attachments are confidential, proprietary, and may be privileged. If this message was misdirected, Barclays Global Investors (BGI) does not waive any confidentiality or privilege. If you are not the intended recipient, please notify us immediately and destroy the message without disclosing its contents to anyone. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of BGI, unless the author is authorized by BGI to express such views or opinions on its behalf. All email sent to or from this address is subject to electronic storage and review by BGI. Although BGI operates anti-virus programs, it does not accept responsibility for any damage whatsoever caused by viruses being passed.
From: CDOLAN [...] cpan.org
On Tue Jan 23 14:54:03 2007, Jeff.Thalhammer@barclaysglobal.com wrote: Show quoted text
> This code: > > $foo{local} = 42; > > falsely reports this violation: > > "local" variable not initialized at line 1, column 6. See page 78 of > PBP. (Severity: 3) >
This already has a TODO test committed in r863 by RJBS. It's a PPI bug. Not sure if it has been reported upstream. -- Chris
This is fixed in PPI 1.2x, which is now on CPAN.