Jan Dubois will give a free workshop at YAPC::NA 2012 described as:
Stackato is a private cloud platform from ActiveState
In this workshop you will:
get a very brief summary of the Stackato architecture
install the Stackato Micro Cloud on your laptop
deploy sample Perl applications (e.g. Bugzilla) to Stackato in minutes
convert your own Perl web applications to Stackato
Preparation
We will have some USB sticks with VirtualBox and Stackato installers available, but to save some time you can also download and install the software ahead of time:
a hypervisor (VirtualBox, VMWare Fusion, VMWare Player)
An article written by brian d foy What if we could drop archives into @INC? got me thinking. Indeed, I've been burned myself by PAR, which is a great instrument, but I don't like that it does a huge unzip every time the application made with it starts. And I don't like even more so that some times PAR forgets to clean up these huge perl trees, eating space in my /tmp.
The problem why it is not that easy to override "use" and "require", is that these are semantic constructs, and are using perl's own file open/close operations, which neither are overridable even with *CORE::GLOBAL:: hack.
Nevertheless, after a couple of days learning about implementation of PerlIO layers and hacking them, the following module was born: File::Redirect. It's basically hacks into open() which is used by perl, and then emulates unix mount semantics.
Here's the Marpa "news" from the past few weeks.
(Marpa is a new, powerful and fast parser and parsing algorithm.
To learn more,
check out
its web page
.)
Revision to the Theory paper
Most of my effort over the past weeks
has gone into a paper
on the math behind Marpa.
I have just uploaded
a revised version.
I've fixed several typos, including a few nasty ones,
for which I apologize.
I've also improved the typography
and smoothed out
the presentation in many places.
The basic structure and results of the paper
are unchanged.
The paper contains pseudocode,
a correctness proof,
and proofs of my complexity claims.
Deleting old releases
I plan to remove official releases
of the various Marpa distributions
(Marpa, Marpa::XS, Marpa::PP)
that are more than one or two versions old.
My guess is that this will release
some disk space, and inconvenience nobody.
I've created a new blog at http://perlservices.at, a site which I intend to use to pimp offer my services, and will use that blog from now on. The design is not quite there yet. :)
London Perl Mongers organises technical meetings every two months. The technical meetings are a chance to find out what has been going on in the Perl community, what techniques people are using and how Perl integrates with other software.
The next technical meeting will be on the 11th April 2012 from 7pm to 9pm (you may arrive earlier, please sign in at the reception). You have to sign up to attend, see below.
This meeting is sponsored by Venda who are inviting the world-renowned Damian Conway to amuse us for one evening and will appropriately be held at the Conway Hall. Many thanks to Anthony Webster, Venda and everyone involved for allowing us to use this wonderful venue.
Venda is a SaaS eCommerce provider with offices in London as well as the US and Asia. The platform is built predominantly in Perl, and powers over 100 sites for clients including Tesco and the BBC.
Damian will be presenting:
Temporally Quaquaversal Virtual Nanomachine Programming In Multiple
Topologically Connected Quantum-Relativistic Parallel Spacetimes... Made
Easy!
As a non native English speaker, writing good documentation is a hard task for me and often grammatical and spelling errors slip into my modules pod causing me great embarrassment.
I could use the spell checker more often*, but writing documentation is already a time consuming task, no fun, and well, I am lazy. In any case, that would not solve the grammatical errors.
The thing is that from time to time somebody sends me a patch correcting some of these errors and I want to say publicly how much I appreciate that kind of contribution.
A special mention goes to the Debian QA team, who seems to systematically revise the documentation of everything packed for Debian. That can't be much fun, but they keep doing it.
So, to all of you who have sent me documentation patches over the years, thank you very much, really.
Maybe this is legitimate and I just don't know why, but I have seen the following in a couple of projects where I have taken over after the original programmer left:
use Moose;
has [qw/foo bar baz/], is => 'rw';
no Moose;
sub something {}
sub somethingelse {}
Tom Christiansen will give a talk at YAPC::NA 2012 described as:
Perl is used in the NLP (natural language community) for a variety of tasks. In biomedical texts, words derived from Latin and Greek pose a big problem for English-language stemmers, because existing standard algorithms like Porter and Snowball fail to produce the base lemmas when faced with irregular plurals.
This talk reviews the problems with existing tools and presents the new Lingua::EN::Biolemmatizer module, which interfaces with the University of Colorado’s “BioLemmatizer” code to produce much more accurate results than were previously available.
You can read about my latest module that helps you archive coverage reports generated with Devel::Cover in this post about App::ArchiveDevelCover on my blog. There is even a screen shot!
ORLite is a light weight SQLite-specific ORM which is particularly handy for working with ad-hoc SQLite database and creating internal database APIs for large applications, most prominently the database API inside of Padre.
Aligning so closely with the features of a single database engine keeps the implementation size down to a minimum, at less than 1000 lines of code, and allows ORLite to do things that would be completely impossible in more general ORMs.
This is particularly true in the upcoming 2.0 release, a preview of which is available now.
This new major revision embraces SQLite's slightly unique rowid mechanism, allowing it to accurately distinguish between different copies of identical data.
Lets start with the following database in the file adam.sqlite
At least that's the goal. I've split Catalyst::Model::REST in two, so there's a new Role::REST::Client as well as the original distribution.
Originally I started CMR because I needed to access some REST services from a Catalyst application. There was nothing useful around, so I wrote a simple Catalyst Model and wrapped it up on CPAN.
It's been further developed to when there has been new requirements, and a couple of days ago the nice people on #catalyst suggested to split the functionality into a distribution of its own. The use case being that a role can be applied to an already existing Catalyst Model. Or to any other class that needs to connect to a REST server.
So here it is. Use Role::REST::Client to access REST services from your Moose based Class.
Use Catalyst::Model::REST if you just want to start a new Catalyst Model Class,
However, we know many of you want to stay in a hotel. So we’ve arranged for an additional block of rooms at another hotel. The Hilton DoubleTree is only five blocks away from the conference facilities, and rooms under our group rate are going for $159 per night. Click here to make a reservation. The group code is TPF. If you want one of these rooms, book fast, or you’ll have to either stay in the dorm, or get a hotel that is farther away. Also, this block of rooms dematerializes on May 10th if they are not already sold out by then.
Thinking about the epigraph of my Perl release started about 10 days before the release. Certainly, I had been unconsciously mulling back and forth about killer
quotes from books or other media for longer than that. About 10 days ago, I made the short list of two books that could give interesting quotes.
One was
"Friday" by R.A. Heinlein. I've always liked the book, and it opens with the introduction of the protagonist as she kills a pursuer and stuffs him into a cabinet, reacting only on a hunch. Heinleins
way of laconic writing should have made for an interesting quote from that scene.
The hackathon and hardware hackathon have proven so popular that we’ve already sold out. However, we’ve acquired an additional room that will be available for hacking through-out the entire YAPC::NA 2012 conference. We did this to ensure there’s always a space to spread out and collaborate on projects.
The hardware hackathon will be freeform for the most part, but if you would like to give a talk or a demonstration on the official schedule, go ahead and submit it. We’ll get it on the schedule. Also, in the notes indicate which of the 5 days of the hardware hackathon you’d like to give your talk. You’ll likely get a bigger audience if you do it in one of the first two days, however, you’d have to have already purchased your badge for the Hackathon since it’s already sold out.
YAPC is nothing if not about collaboration and sharing ideas. We want to make sure everybody has that opportunity, so that’s why we’ve extended the Hackathon to be all 5 days.
Today we can find a lot of presentations written in HTML or any other variant (XHTML, HTML5, etc) using JavaScript frameworks such as s5 or deck.js.
These frameworks allow the creator to do advanced presentations with simple HTML. This has a lot of advantages as the user
is in full control of the layout
can easily embed images, links, code, etc
can use a revision control tool
Although one major drawback of such frameworks is sharing the slides. Of course the slides can be put online on any HTTP server and be easily read from a browser, but not everyone has access to a public web server.
Every time I review code others have written, I blame people for doing date arithmetic of their own. However, some time ago, I received a pull request for a module that had some date arithmetic inside. As all tests passed, I could not see something dangerous in it and followed the pull request. Today, I found the date tests failing. Why? Why today? Well, this is worth some investigation.
The main part of the module generates an HTTP-Header using this construct ($c is the mocked catalyst context, expire_in is a method containing the nr of seconds to expire in):
$c->response->headers->expires(time() + $self->expire_in)
if ....some_condition...
Well, adding a number of seconds to an epoch value cannot hurt. Can it? The test looked like this:
I released Test::File 1.33 yesterday, which fixed a minor MANIFEST glitch with 1.32, which I released three days ago. (I know it’s been discussed before, but I guess I never really appreciated it: it sure would be nice if CPAN Testers could report stuff like that). Version 1.32 fixes a number of CPAN RT tickets (in fact, it pretty much closes out all the open bugs), most of which you won’t care about. If you happen to be using Windows, this may fix a number of test failures, although there are still a few left that I’m working with schwern to fix. (If you are running Windows and you happen to see some mysterious errors which boil down to the fact that “skip” isn’t the same as “SKIP”, it’s definitely safe to ignore those.)