The Vagrant PDE is a VirtualBox image ready for Perl development with many of the CPAN modules you'd want to use.
Upgraded the Operating System to Ubuntu 2015.04
Added Rakudo Perl 2015.09
Added several Perl Modules
Upgraded all the other Perl Modules
If you have never used it, you can follow the instructions for the Vagrant Perl Development Environment.
If you already have the previous version installed, you can follow the instructions
to upgrade PDE.
Anybody want to be an organizer for YAPC::NA? We're open to anybody that wants to help out. Really, our only rule is that you have to help out. We don't want to be organizing in front of spectators / peanut gallery. If you are willing to roll up your sleeves and do some work, we're happy to have you. Our next planning meeting will be in a couple weeks. If you want to participate, please complete the doodle poll prior to Monday, October 5th:
The goal of Hacktoberfest is to get more people contributing to open source by submitting at least one pull request (PR) during the month of October. If you sign up and do at least four PRs in the month, then you'll get a free t-shirt.
At MaxMind, we created the MMDB format because we needed a format that was very fast and highly portable. MMDB comes with supported readers in many languages. In this blog post, we'll use Perl modules to create an MMDB file which contains an access list of IP addresses. This kind of database could be used when allowing access to a VPN or a hosted application.
I have started compiling summaries of the Perl 5 Porters (p5p) mailing list. Thank you to everyone who helped improve them. Following is the first report.
My August assignment (yes, I had to "stick" with it for September) in the CPAN Pull Request Challenge was Test::Aggregate. In August, I went on vacation, and CPAN Testers' reporting was down, so I decided to solve the task after I return from the YAPC in Granada and ask for a new distribution for September with a two-week delay. It wasn't that easy, though.
When I started working on P6SGI, I thought, "Hey, I'll just update PSGI to use
Perl 6, take advantage of some async data structures, and be done." That is
not how this process has gone down. First, I learned that I needed to know
more about Perl 6. Then, I found that I need to know more about HTTP/1.1 and
more about PSGI. Most recently, I have been researching HTTP/2, Mojolicious,
WebSockets, Akka, and a whole pile of other things.
So, here's the progress report on thing that have changed in the last week or so
on our way toward a complete P6SGI standard, which is still a ways off.
So I really like to validate email addresses using Email::Valid. But yesterday, I got a bug report. Some system was sending emails to another system with addresses containing a space right after the @. That other system was totally unable to deal with those.
"But I do email address validation" I thought. "Not just with a stupid regular expression like .+\@.+, but with Email::Valid". So I added a test to our suite and sure enough, that new test failed.
Lesson learned: Read the documentation of the modules you use.
Just to give people an update on where I am after the spill and subsequent events at YAPC:
First of all, I need *AGAIN* to give my thanks to:
@Amal1a_ (Amalia) (and everyone else at Evozon for supporting me)
@renatolrr - (Renato) YAPC Coordinator, gofer and frequent bedside supporter during the last 3 weeks of hell
@Makova65 - (Manu) Another bedside confidante and inadvertent Andalusian Spanish tutor
@jjmerelo - (JJ Merelo) Another coordinator, gofer and @YEF director, I think.
And those that I can't find on Twitter - Maribel, Victor, Pablo, Paloma and Jose. Pretty much everyone responsible for YAPC::EU 2015, probably.
I can't thank you enough, you made my last 3 weeks bearable, I'm not sure what I would've done if I were just staring at off-yellow hospital walls for 3 weeks. I *SHALL* return to Granada, and Manu, I *will* take you up on your offer.
[This is the first post in a new, probably long-ass, series. I do not promise that the next post in the series will be next week. Just that I will eventually finish it, someday. Unless I get hit by a bus.]
The topic arose at $work recently: what do the cool kids use for dates these days? Our sysadmin was looking for a simple way to get “tomorrow.” Of course, the cool kids are theoretically using DateTime, right? So, how do we get “tomorrow” out of DateTime? The answer came back in our chat room:
Datetime->now->add(days=>1)
Well, okay ... that would work. But it’s not exactly what I’d call “easy.”
We immediately reached our minimum of $1,701; now our goal is to reach $20K in the next 9 days. We can do it... WITH YOUR HELP!
STEP 1: Make a generous pledge.
STEP 2: Get your friends to match your pledge.
STEP 3: Get your boss to double your pledge.
STEP 4: Go back and increase your pledge.
STEP 5: PERL WILL BE THE FASTEST LANGUAGE EVER.
Thanks so much for your continued support of RPerl!
I just tried to add perl 5.22 to the list of perl I run my tests on, but it seem Travis-CI does not support perl 5.22 yet.
This reminded me that it would be nice if I could configure Travis-CI to use a flag such as 'latest_production' that will always use the latest version of perl available in Travis-CI so when the finally add 5.22 the "latest_production" will automatically pick up that version.
It would be also great to have 'blead' that would use blead perl for testing.
I've been working on a Bayesian spam filter, but it keeps running out of memory, so I moved to something else for a while. The new concurrency stuff looks really interesting, but I don't understand it well yet. As a project, I came up with the idea of a password cracker, which would check a crypt-style hash against a word list. (This probably isn't a CPU-intensive enough task to be worth threading, but it was simple.) Here's the code, with details below:
