develooper Front page | perl.perl5.porters | Postings from June 2018

[perl #132528] Bleadperl v5.27.5-396-gdd6661605f breaksVPIT/B-RecDeparse-0.10.tar.gz

From:
slaven@rezic.de via RT
Date:
June 2, 2018 08:22
Subject:
[perl #132528] Bleadperl v5.27.5-396-gdd6661605f breaksVPIT/B-RecDeparse-0.10.tar.gz
Message ID:
rt-4.0.24-32117-1527927754-1832.132528-15-0@perl.org
Dana Mon, 23 Apr 2018 05:11:17 -0700, davem reče:
> On Mon, Apr 23, 2018 at 10:35:26AM +0200, Sawyer X wrote:
> > 
> > 
> > On 04/23/2018 10:33 AM, Dave Mitchell wrote:
> > > On Sun, Apr 22, 2018 at 09:20:54AM +0200, Sawyer X wrote:
> > >>
> > >> On 04/21/2018 05:18 PM, Dave Mitchell wrote:
> > >>> On Sat, Dec 02, 2017 at 03:15:35PM +0000, Zefram wrote:
> > >>>> Andreas J. Koenig via RT wrote:
> > >>>>> A not very surprising BBC:
> > >>>> Needs examination by Vincent.  It's not surprising that a change
> > >>>> to B::Deparse would break some oversensitive test, but this one
> > >>>> doesn't look exactly like that.  B::RecDeparse doesn't look like it
> > >>>> should be that sensitive, and the way the tests are failing is funny.
> > >>>> But B::RecDeparse's relationship to B::Deparse is quite convoluted,
> > >>>> and I can't readily see what's going on.
> > >>> I don't think this ticket should be a 5.28.0 blocker
> > >> Because of the tight relationship between B::RecDeparse and B::Deparse?
> > > Yes.
> > 
> > This is reasonable. I just wanted to be sure.
> > 
> > I think any module in which you're depending on internal state, you are
> > in charged with updating your code. Equivalent to any other module that
> > has the purpose of exposing the current OPs. If they change, it needs
> > updating.
> 
> I've now removed it from 5.28 blockers
> 

What's the resolution here? Should a ticket in the CPAN module's queue be opened?



---
via perlbug:  queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=132528



nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About