Re^9: $1 not "freezing" in an addition

How is P::C to descend into code that's not loaded until runtime?

It could, wait for it, load the code

do the scandeps dance

not do anything at all

How is P::C to descend into compiled code that's not loaded until runtime and for which the source code is not available?

Who said P::C is supposed to do it ?

How do you know you've caught every global? How do you know stringification is desirable?

Clearly stringification of $1 is undesireable -- I am humbled by your logic

Comment on Re^9: $1 not "freezing" in an addition

Replies are listed 'Best First'.
Re^10: $1 not "freezing" in an addition by chromatic (Archbishop) on Dec 16, 2012 at 01:43 UTC
If your answer to "How is Perl::Critic to do this thing?" is "Magic", then I'd very much like to see your implementation. Clearly stringification of $1 is undesireable... Giving the wrong answer sometimes is undesirable. Giving the wrong warning doubly so.	[reply]
Re^11: $1 not "freezing" in an addition by LanX (Saint) on Dec 16, 2012 at 02:15 UTC
Hei chromatic, apply some magic and better ignore this anonymous troll! =) cheers Rolf	[reply]
Re^12: $1 not "freezing" in an addition by Anonymous Monk on Dec 16, 2012 at 02:42 UTC
Apply some magic and better ignore the troll! =) Anonymous Monk expresses a few simple ideas and chromatic has to start conflating them on purpose `$1 ... foo()` there is no ambigiuity, the potential exists for this bug so what is the problem with a user asking for extra warnings, extra debugging mode, extra potential criticism, even if they don't cover 100% of all situations, even if they can be wrong, even if it requires a special compile of perl for descend into xs, or running scandeps, or whatever? oh right, must be a troll	[reply] [d/l]
Re^13: $1 not "freezing" in an addition by LanX (Saint) on Dec 16, 2012 at 03:23 UTC
Re^14: $1 not "freezing" in an addition by Anonymous Monk on Dec 16, 2012 at 03:33 UTC
Re^14: $1 not "freezing" in an addition by Anonymous Monk on Dec 20, 2012 at 04:48 UTC
Re^11: $1 not "freezing" in an addition by Anonymous Monk on Dec 16, 2012 at 02:05 UTC
If your answer to "How is Perl::Critic to do this thing?" is "Magic", then I'd very much like to see your implementation. Do what? Giving the wrong answer sometimes is undesirable. Giving the wrong warning doubly so. Gee, if only perlcritic had some way to differentiate levels of warnings ... no, it must always be 100% perfect	[reply]