May 7th, 2002



I'm rewriting one of my oldest Perl projects (BML), making it work with mod_perl.

Goddamn my Perl was ugly back then. I wrote that in July of 1997. My style and skills have changed a bit in 5 years. :-)

Hell yeah

For the past ~4 hours I've been rearranging and rewriting BML.

I didn't even try to perl -c it until about an hour ago. About 5 minutes ago it got syntactically correct. (I was using perl -c to point me at the next uncompleted area, after I got the major structure down.)

Anyway, after it became syntactically correct I thought, "No way in hell this can work... let's see." Start tailing the error log... restart webserver... hit a page. Error. I start thinking: Yeah, this is gonna take awhile.

Fix the error (trivial). Restart. Reload. Prepare myself for the next error.
But, no... it just works. How cool is that?

Oh, there are still a billion things I want to do (like always), but it's basically done.

Best things: learning new APIs & cleaning/killing old, ugly code. At the same time? Bliss. :)

Think I'm going to go running. Time to get off my ass.


Went running, showered, then hung out with rivulet... we did a whole lot of nothing, highlights being pool, pizza, and beer, which in retrospect sounds like more than nothing, so hooray.

More BML mod_perl-ing afterwards. Kickin' some ass.

A little known feature of Perl is that when lexically defined variables go out of scope, any indirect filehandle stored in them is automatically closed. So, in fact, there's really no reason to perform an explicit close() on the filehandles in the two preceding examples unless you want to test the close operation's return value.
I found them stating that humorous, given that Linux's close() always returns true.