Multimethods
Normally I save up blog posts and consolidate them into long ones, but apparently we get to see mst++ cross-dress if I blog once a week. So this post will be less content-rich than usual, but it's for a good cause. Anyway, I started writing a new application tonight called PleasureChicken. The details of what PleasureChicken does is an article for another day, but basically, any entity in Pleasure
Unshortening URLs with Modern Perl
Tiny URLs, like the ones Twitter uses, have been stirring up a lot of controversy lately. People wonder what will happen if the tiny URL service goes down, goes away, or goes rogue. The links in their Twitter posts could become useless, and that would be tragic. This is a problem that's easier to work around than to whine about, so I've implemented a web service that unshortens any short URL. You
More cperl-mode enhancements
I've been working on cperl-mode.el, the Emacs mode for editing Perl, again. It now comes in two flavors -- plain Perl, and Moose. The plain Perl version has not changed much in the last year, it is the same cperl-mode that you all know and love, but with support for all Perl 5.10 features. You can get that branch here: http://github.com/jrockway/cperl-mode/tree/master The interesting thing, though
Problems with Lisp
I have seen a few complaints about Common Lisp over on Programming Reddit this week. Most of them are the usual kind of complaints you hear from people that are new to any programming language ("I don't understand the common idioms, so the language is bad"), but one complaint keeps coming up: Lisp doesn't support hashes well. There are plenty of things wrong with Lisp, but I don't get this one. So
Myth: Moose is an unnecessary dependency
It always strikes me as odd how people single out Moose as a dependency they're afraid to use or introduce into their application. One of the arguments I've heard is "I don't want to make something overly complex with dependencies that don't relate to the task". I think this view is misguided, because the alternative is to add unnecessary code and tests to your application. The best code is code t
Iterators in elisp
A long time ago, before I knew elisp, someone told me to never use lexical-let. I've ignored their "advice" and have written this: (require 'cl) (defun get-iterator-over-words-in (buffer) (lexical-let ((buf buffer)(pos 1)) (lambda () (save-excursion (let ((cur (current-buffer)) result) (switch-to-buffer buf) (goto-char pos) (forward-word) (let ((pt (point))) (if (not (eq pos pt)) (progn (setq res
Emacs and Perl 5.10
Earlier this week, I took cperl-mode and added support for the new 5.10 features. It now knows how to highlight state, //, say, and given/when/default blocks. It also highlights method as though it were sub, because I'm using Schwern's Method::Signatures module pretty heavily now. You can get my hacked version from http://git.jrock.us/?p=elisp.git;a=blob;f=cperl-mode.el;hb=HEAD I haven't official
Git merging by example
This is Jonathan Rockway's blog, where he talks about Angerwhale, Catalyst, and Everything. UPDATE (28 Apr 2008): So apparently this article made it to the front page of delicious, reddit, and hacker news. It's always the ones I least expect :) Anyway, I've updated the branch names to be less confusing, and I've added an explanation of why I say git ci instead of git commit; I have the following s
cperl-mode.el and Moose
I have recently started using MooseX::Declare, and decided to update cperl-mode.el to support all of the Moose keywords. You can get my version of cperl-mode.el (which was also updated to support perl 5.10 keywords a while back) from http://git.jrock.us/?p=elisp.git;a=blob_plain;f=cperl-mode.el;hb=HEAD. If you are wondering what it will look like, I made a sample with htmlize: http://jrock.us/cper
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Increment test counter