Front page | perl.perl5.porters |
Postings from April 2016
On Mon Apr 11 00:41:51 2016, kentfredric wrote: > There's been a lot of idle chat about this, but not any real > commitment to a resolution either to block, or to vocally state an > intent to release with a known broken and significant module. > > - https://rt.cpan.org/Ticket/Display.html?id=112246 > > - Scope::Upper is broken because of Stack Context Changes > - There is a respectable number of consumers of Scope::Upper, > including: > > -- Dancer2 To clarify this, Dancer2 does *not* use Scope::Upper. It uses Return::MultiLevel which *might* use Scope::Upper if it's available. When you install Dancer2, it will pull in Return::MultiLevel which doesn't *require* Scope::Upper. If you try to install Scope::Upper it will fail (hence this ticket), but Return::MultiLevel will just use a Pure-Perl implementation (because mauke is awesome) and Dancer2 will simply use that. It's important to note, this does not break Dancer2. It does make it slower by making Return::MultiLevel slower. Or, more accurately, does not allow it to be faster by utilizing Scope::Upper. --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=127875Thread Previous | Thread Next