Aaron Crane

• Website: aaroncrane.co.uk/
• About: I blog about Perl.

Recent Actions

• 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,...

Comment Threads

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

  Look what we did... Oh well.

  To Cladi.it, I hope you're not too discouraged and still doing Perl wherever you are right now. It's a fun and great language. And in fact, the community is much better now than it used to be, despite your particular experience here. Trust me.

• 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.