ribasushi

• A while ago Coro gets a bugreport about XS-level signal handlers and Perl-level signal handlers going out of sync
• Coro's author reaches deep into perl internals to patch this up for the runtime, writes extensive tests for it, fixes the Coro-level manifestation
• in 5.21.8 the hook interface is removed in order to (sic) save 4k of memory PER PROCESS: https://github.com/Perl/perl5/commit/c910fead7893
• A ticket is raised against 5.22.0-to-be, and dies after some discussion: http://www.nntp.perl.org/group/perl.perl5.porters/2015/05/msg228257.html
• The issue is however acknowledged but not much is done to fixing it https://rt.perl.org/Public/Bug/Display.html?id=125439
• As a result Coro as a toolkit can either
  • remove a part of its tests and continue being buggy under a known use scenario
  • refuse to build on 5.21.8+ until either P5#125439 is resolved or c910fead7893 is rolled back
• The author chose the second option (which is exactly what I would do myself in his situation)
• The "stableperl fork"

ribasushi

Yet Another Perl Podcast: Perl 7 & Pragmatic Perl & etc.

This is an English transcript of the 17th issue of a Russian podcast Yet Another Perl Podcast, recorded on the 17th of April 2013 and aired on April 28th. The original audio of the podcast is available at its official site. The recording is also available for direct mp3 download.

ribasushi

<p>I can not think of anything qualifying as <i>doesn't have to be a huge Perl project</i>* However, I have an idea which unquestionably will benefit the Perl community immensely, yet has a remarkably low barrier to entry (mainly one thing - patience). I propose that someone applies for a grant in the role of <b>DBIx::Class re-documentation project lead</b>.

<p>I have had inklings of "there got to be a better way to do things", but it wasn't until I read <a href="http://www.perlmonks.org/?node_id=1133234">this meditation by BrowserUK</a> that it dawned at me: Fixing up the better-than-most-but-still-terrible documentation of DBIC is a ~200 person-hour undertaking, which on top of that requires someones fresh eye. Given that DBIx::Class is a "staple-module" in the contemporary Perl ecosystem, I believe it is reasonable to expect for the TPF to "pick up the tab" if someone with the right qualifications steps up.


<p>What is wrong with DBIC's documentation anyway?
<ul><li>Lack of entry level architectural docu

ribasushi

*.html binary

ribasushi

#!/usr/bin/env perl

use warnings;
use strict;

use Carp 'cluck';

sub worker {
  my $ctx =
    defined wantarray.

ribasushi

33
68
68
64
68
68
28
319
56
57