Bug #82043 for Method-Signatures: Fails with bleadperl since v5.17.0-360-g9da1dd8

Mon Dec 17 02:20:20 2012 ANDK [...] cpan.org - Ticket created

Subject:

Fails with bleadperl since v5.17.0-360-g9da1dd8

Bisect reveals: commit 9da1dd8f41c98df713957a658aa8fefcdf57163c Author: David Mitchell <davem@iabyn.com> Date: Sat Jul 23 21:29:02 2011 +0100 make re_evals be seen by the toker/parser Link to the commit: http://perl5.git.perl.org/perl.git/commit/9da1dd8f41c98df713957a658aa8fefcdf57163c My fail report has not yet arrived at cpantesters. HTH, Let me know if you need more,

Mon Dec 24 00:35:34 2012 BAREFOOT [...] cpan.org - Correspondence added

Show quoted text

> make re_evals be seen by the toker/parser > > Link to the commit: >

http://perl5.git.perl.org/perl.git/commit/9da1dd8f41c98df713957a658aa8fefcdf57163c Hmmm ... I _think_ what's going on here is that this commit somehow makes the parser try to parse the signature before Devel::Declare gets a shot at it. Am I right? If so, that seems like incorrect behavior. My understanding of the way Devel::Declare works is that as soon as the parser sees the keyword trigger, it should stop parsing and let the DD code take over. So, what's the proper resolution of this?

Mon Dec 24 00:35:35 2012 The RT System itself - Status changed from 'new' to 'open'

Thu Sep 26 03:32:36 2013 BAREFOOT [...] cpan.org - Correspondence added

I don't believe this is still happening with 5.18. I'm going to go ahead and resolve it for now; if it's still a problem, we can always reopen it.

Thu Sep 26 03:32:37 2013 BAREFOOT [...] cpan.org - Status changed from 'open' to 'resolved'