Closed p5pRT closed 9 years ago
The use strict in subroutines is real nice at telling me variables that have not been specified properly.
It doesn't seem to say anything about extra specifications of variables that are not used in the routine. This makes it harder to make sure everything is "clean". Generally this happens after you write the routine and then make changes later. You forget to go remove the "my $vars".
It would be nice if the compiler would let us know about them.
On Fri May 31 06:17:03 2002\, warrend@mdhost.cse.tek.com wrote:
This is a bug report for perl from warrend@tek.com\, generated with the help of perlbug 1.33 running under perl v5.6.1.
----------------------------------------------------------------- [Please enter your report here]
The use strict in subroutines is real nice at telling me variables that have not been specified properly.
It doesn't seem to say anything about extra specifications of variables that are not used in the routine. This makes it harder to make sure everything is "clean". Generally this happens after you write the routine and then make changes later. You forget to go remove the "my $vars".
It would be nice if the compiler would let us know about them.
This motion for an enhancement to 'strict' has failed to receive a second in more than twelve years. I recommend that the ticket be closed.
Thank you very much. Jim Keenan
On Fri May 31 06:17:03 2002\, warrend@mdhost.cse.tek.com wrote:
This is a bug report for perl from warrend@tek.com\, generated with the help of perlbug 1.33 running under perl v5.6.1.
----------------------------------------------------------------- [Please enter your report here]
The use strict in subroutines is real nice at telling me variables that have not been specified properly.
It doesn't seem to say anything about extra specifications of variables that are not used in the routine. This makes it harder to make sure everything is "clean". Generally this happens after you write the routine and then make changes later. You forget to go remove the "my $vars".
It would be nice if the compiler would let us know about them.
This motion for an enhancement to 'strict' has failed to receive a second in more than twelve years. I recommend that the ticket be closed.
Is this is asking for Perl to detect variables declared but not used?
That might be difficult for certain cases and possible in others.
But I can hardly see making it a fatal compilation error in the default case. Perhaps it could be a warning at best.
--tom
* Tom Christiansen \tchrist@​perl\.com [2013-02-24T19:58:56]
This motion for an enhancement to 'strict' has failed to receive a second in more than twelve years. I recommend that the ticket be closed.
Is this is asking for Perl to detect variables declared but not used?
That might be difficult for certain cases and possible in others.
But I can hardly see making it a fatal compilation error in the default case. Perhaps it could be a warning at best.
I believe this is a duplicate of https://rt-archive.perl.org/perl5/Ticket/Display.html?id=5087
-- rjbs
On Sun Feb 24 15:44:28 2013\, jkeenan wrote:
On Fri May 31 06:17:03 2002\, warrend@mdhost.cse.tek.com wrote:
This is a bug report for perl from warrend@tek.com\, generated with the help of perlbug 1.33 running under perl v5.6.1.
----------------------------------------------------------------- [Please enter your report here]
The use strict in subroutines is real nice at telling me variables that have not been specified properly.
It doesn't seem to say anything about extra specifications of variables that are not used in the routine. This makes it harder to make sure everything is "clean". Generally this happens after you write the routine and then make changes later. You forget to go remove the "my $vars".
It would be nice if the compiler would let us know about them.
This motion for an enhancement to 'strict' has failed to receive a second in more than twelve years. I recommend that the ticket be closed.
A year-and-a-half later\, this feature request still has not received a second. Marking ticket rejected.
Thank you very much. Jim Keenan
@jkeenan - Status changed from 'open' to 'rejected'
Migrated from rt.perl.org#9426 (status was 'rejected')
Searchable as RT9426$