On Wed, Oct 24, 2012 at 1:31 AM, Shmuel Fomberg <shmuelfomb...@gmail.com> wrote: > Hi David. > > On Wed, Oct 24, 2012 at 5:19 PM, David Oswald wrote: >> >> I spent a couple of hours updating List::MoreUtils to fix RT#75727, >> RT#78527, and RT#76749. I've placed the work in a public Github >> repository here: > > > About your pairwise $a and $b fix - I see that it is some code executed only > if the first 'use' statement is importing pairwise. > What will happen when a second module will want to import and use this > function? > What will happen when the first module did not imported it, but the second > module did? > > Is it really the way to solve this problem? > > Shmuel.
That's an interesting consideration, and I'm glad you mentioned it. There doesn't seem to be a convenient way of simple disabling the warning in any package that imports 'pairwise' (at least I know of no way to affect the warnings in the lexical scope of the callback sub provided to pairwise). So instead, touching $a and $b in any package that imports pairwise seemed to be a reasonable solution. But perhaps it needs to be done inside the pairwise function so that when it's invoked it affects the 'touch' in its caller's package. If you have a proposal I'll gladly push it to the repo. Not sure if anyone's going to use it anyway, but at least we're trying to get the ball rolling again. -- David Oswald daosw...@gmail.com
