Versioned <tt>site_lib</tt>
Today I wanted to install a simple module on a production machine. I used the CPAN utility, as usual. Unfortunately that also pulled in an upgraded dependency which was not backwards compatible, breaking the application. I hate yak shaving. But not nearly as much as I hate surprise yak shaving. I want to fix compatibility problems in my development environment on my own time, not hastily on a live
Event driven PSGI
I spent most of today and yesterday bikeshedding event driven PSGI with miyagawa on #http-engine. We seem to have converged on something that is both fairly portable to different event driven implementations, without being too yucky for blocking backends. For example, if you don't yet know the response code or headers and are waiting on some other event driven thing, it's sort of like continuation
Roles and Delegates and Refactoring
Ovid writes about the distinction between responsibility and behavior, and what that means in the context of roles. He argues that the responsibilities of a class may sometimes lie in tangent with additional behaviors it performs (and that these behaviors are often also in tangent with one another). Since roles lend themselves to more horizontal code reuse (what multiple inheritance tries to allow
IO::Handle::Util
My friend miyagawa has been championing PSGI and its reference implementation, Plack. This is something we've needed for a long time: a clean and simple way to respond to HTTP requests without the cruft of CGI and %ENV. The PSGI specification requires the body of the response to be represented using an object similar to IO::Handle. I've released IO::Handle::Util, a convenience package designed to
Cache Assertions
Caching an expensive computation is a great way to improving performance, but when it goes wrong the bugs can be very subtle. It's vital to be sure sure that the cached result is, for all intents and purposes, the same as what the computation would have produced. A technique I often employ is using a thunk to defer the computation: $cache_helper->get_value( $key, sub { ... produce the expensive re
<tt>Try::Tiny</tt>
I just released Try::Tiny, yet another try { } catch { } module. The rationale behind this module is that Perl's eval builtin requires large amounts of intricate boilerplate in order to be used correctly. Here are the problems the boilerplate must address: $@ should be localized to avoid clearing previous values if the eval succeeded. This localization must be done carefully, or the errors you thr
PL_runops
I'm going to try to do a series of posts about learning Perl internals. I am still a beginner, I have trouble remembering the many macros, or keeping everything in my head all at once, so hopefully I will be able to make some sense of this stuff in a way that is accessible to other beginners. While I'm definitely diving right in to the deep end, I think PL_runops is a good place to start as any, t
SV *
In my last internals post I mentioned that most of the data in Perl revolves around the SV struct. The excellent PerlGuts Illustrated describes these structures in great detail, and of course there's the two main documents in Perl's own reference, perlguts which tells you about them and perlapi which tells you what you can do with them. This post is sort of like PerlGuts for dummies, intended to l
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
