Re: use Ensure -- module to spot undefined stuff

Replies are listed 'Best First'.
Re^2: use Ensure -- module to spot undefined stuff by gone2015 (Deacon) on Aug 06, 2008 at 07:59 UTC
`strict` will throw out undefined/misspelt variables, but subroutines are left to be found at run-time (except for barewords). I agree that `strict` should do this, but it doesn't.	[reply] [d/l] [select]
Re^3: use Ensure -- module to spot undefined stuff by Fletch (Bishop) on Aug 06, 2008 at 15:13 UTC
Ah, so the question becomes what does this do that B::Lint doesn't do (other than being fatal rather than printing a warning, that is)? `$ perl -MO=Lint -wce 'foo( );' Nonexistant subroutine 'foo' called at -e line 1 -e syntax OK` [download] The cake is a lie. The cake is a lie. The cake is a lie.	[reply] [d/l]
Re^4: use Ensure -- module to spot undefined stuff by gone2015 (Deacon) on Aug 06, 2008 at 16:15 UTC
`B::Lint` only considers `main` (at least by default), which doesn't quite fit with an Object approach. As with `use strict`, I am surprised that there isn't something more built-in to cover the horribly common case of misspelling a subroutine name -- especially as the error can lie dormant in a little used part of one's code ! If `use strict` covered it, or if `B::Lint` was easier to use and could be specified within packages, then this module would be redundant.... In the meantime, I've found it useful and the reason for this posting is to see if other people would too.	[reply] [d/l] [select]
Re^5: use Ensure -- module to spot undefined stuff by Fletch (Bishop) on Aug 06, 2008 at 17:18 UTC
Re^6: use Ensure -- module to spot undefined stuff by gone2015 (Deacon) on Aug 07, 2008 at 00:05 UTC