user-pic

Aaron Crane

  • Posted blogs.perl.org security breach to Meta

    We regret to announce that blogs.perl.org was recently the subject of a data

    An attacker gained access to the database that runs the site, and was able to take a copy of all users’ hashed passwords. We’ve therefore cleared all users’ passwords as a precaution.

    If you …

  • Commented on New feature: automatic post truncation
    We honour a split provided by the author, but only as long as the non-extended part still falls within the hard limit. My reasoning for that was to avoid any problems in the face of a long piece with an...
  • Posted Perl 5.17.8’s release epigraph to Aaron Crane

    Cross-posted from my other blog.

    Yesterday I had the pleasure of releasing version 5.17.8 of Perl. Perl has had regular, time-bo…

  • Commented on Text Processing: Divide and Conquer
    Hi, Kirk. Here’s an alternative approach that you may find interesting. I don’t have exactly the same data set as you to test against, but I reconstructed a similar case, and this takes about 205ms (on my machine, under 5.16.0)...
  • Commented on A Look At Braces
    Here's another one: iteration in globbing. $ perl -lwe 'print for <a{x,y,z}b>' axb ayb azb...
  • Posted New feature: front page pagination to Meta

    Some of you may have noticed that the blogs.perl.org front page recently acquired a new “Page 2” link. This is a feature we’ve been wanting for quite some time, to help readers scan back through the thousands of entries our users have posted in the nearly three years we’ve been…

  • Commented on Monkey-patching, subclassing, and accidental overriding
    Hi, Ovid. Thanks for the idea. Is warning (rather than throwing an exception) the right thing in your situation? My inclination is to make it an error, like the error you get when the class being patched contains a method...
  • Posted Monkey-patching, subclassing, and accidental overriding to Aaron Crane

    One of the great things about open-source software is the ability to reuse using a class that doesn't have quite enough features for what you're trying to do. What's the best way to deal with that sort of situation?

  • Commented on Can we afford bad code on blogs.perl.org?
    Hi, confuseAcat. If I understand you correctly, you’re saying that this blog should be forbidden in some way. I’m totally against that; I think there’d need to be a really good reason for us to take down someone’s blog (libel,...
Subscribe to feed Recent Actions from Aaron Crane

  • leonerd commented on Can we afford bad code on blogs.perl.org?

    Cats with poor grammer?
    ITYM grammar. :)

  • Blog commented on Can we afford bad code on blogs.perl.org?

    Thank you all for your support. I plan to go to continue to learn perl and my posts are back online, All constructive comments are welcome. A community is made ​​to grow together.
    See you on the blog! ;)

  • Ovid commented on Monkey-patching, subclassing, and accidental overriding

    The idea behind the warning is simple: never break production. For a related module, see Devel::Deprecate and how I handled it there. You probably won't kill anything by upgrading a module you've monkey patched, but if the code you've made the monkey patch with is what kills the Web site, people are going to be very unhappy with you.

    In short: never, never, never break production by accident. You break it very deliberately when you *know* that you have no choice but to break it.

  • wirespeed.wordpress.com commented on Text Processing: Divide and Conquer

    It would be interesting to see how Regexp::Assemble fares against these alternatives. All you would have to do is plug the following in:


    use Regexp::Assemble;
    my $regex = Regexp::Assemble->new->add(@patterns)->ra;

    ... at the top of Aaron's (most excellent) suggestion. Although while on 5.8 this will be much faster, from 5.10 onwards it will be slower, so not much win. It would be much more so if the patterns were regular expressions themselves.

  • Peter Rabbitson commented on New feature: automatic post truncation

    I understand that there are "two right answers" in this case, so do what you think it's best. Just one last idea for the problem of "900-100" split - simply add a rule of at least 40%/60% split if body and extended are both populated. Perhaps also raise the hard limit to 500 words.

    Cheers!

Subscribe to feed Responses to Comments from Aaron Crane

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.