Posts by Yanick Champoux
Anybody with a sensible bone in their body would have written a small script to turn a snippets file into an html file and be done with it. Me, I saw an opportunity to work a little more on my Template::Caribou pet project. Bottom-line: there is now the files snipmate_cheatsheet.pl and snipmate_index.pl in Template::Caribou’s repo. They can be used straight from the repo checkout as follows:
A new trial version of DBD::Oracle is on CPAN. The meat of this release is the awesome work Martin Evans did in the murky core of the beast. He explains it better, but basically his magic results in a much faster DBD::Oracle on thread-enabled perls. This being said, the changes he did are significant (2.3K lines changed according to Git), and we would be very grateful of anybody finding the time to try and install that trial version before it goes live
By now, I have a few Dist::Zilla plugins interacting with the distribution’s changelog. Each time, I get the changelog, I parse it into a CPAN::Changes object, do something to it and save it again. It’s actually not even as hard as it sounds, have a look.
Today I got an email reminder that the Metacpan logos are all in and that the voting booths are open, and will be so until Friday the 30th of March 2012, 23:00:00 UTC.
The pièce de résistance is Dist::Zilla::Plugin::NextVersion::Semantic which I had promised to Mike Doherty a long time ago. In a nutshell, the plugin examines the changes of the upcoming release and increases the version according to the rules of semantic versioning.
I’m in the throes of a major redesign of the site of my comic book, Académie des Chasseurs de Primes. Like any of those redesign, it involves a lot of CSS whack-a-mole. Fine-tuning one page throws a second one slightly off another, and fixing that second one causes unforseen effects on a third one. And so on, and so bloody forth. Generally, to discover those oopsies, I have to navigate the whole site. Bah, humbug. Wouldn’t it be much efficient to have a single document showing all of the site’s page? Something like a contact sheet for the website, if you will. Well, let’s see how hard that would be.
I have a Person class, and I want to know if they can pass the butter. So far, it’s hardly a problem,But here’s the rub. If $georges can’t pass the butter, I want to know why. Is it because he’s too far away, because there is no butter on the table, because he doesn’t like me, or any other reason? What is the most elegant way of knowing the if and the why?
The extension system is good for anything written in C. So, in theory, I could — probably shouldn’t — but I could write a thin wrapper for a Perl interpreter. At that point, I had no choice. The idea was so preposterous, I had to try it.
What if I found a way to get the blog entries, and plop them on mailboxes on my mail server? That would take care of ubiquitous access. And since I would have control on the software, I could probably manage to filter out dupes. I sat down and began to hack on this. The result is mailfeed (clever project name pending). I’m still not sure if it’s a good idea, but at least its execution showcase how much niftiness can be crammed within 144 lines of code. But let me show you…
My first stab at SQLiteTAP is on GitHub. I’m writing it as a SQLite extension, so I had to brush up very rusty C skills. But after a few hours pouring over the documentation, and poking here and there, I have a working implementation of ‘plan’ and ‘ok’. Nothing earth-shattering, I’ll concede, but a nice start nonetheless.