This tutorial will first provide an overview of the Catalyst infrastructure and design as it exists in the 5.80/Moose world, and describe how things have changed since 5.70 and what you need to be aware of as potential gotchas when upgrading applications built for earlier versions.
Then we’ll cover the new features added directly and indirectly through the upgrade to Moose, and how these new means of using and extending Catalyst lead to new best practices for extending applications and managing complexity and maintainability over time.
There will be a practical component to this tutorial; attendees will be expected to have some knowledge of using Catalyst and a recent install on their laptops if they are going to be able to follow the exercises.
Matt S Trout was thrust into Perl at the tender age of 17 by a backup accident. Two weeks later he realised that he was in love with the language and has been happily using it for systems automation, network, web and database development ever since.
He is a core developer (and repository admin) for the Catalyst web framework, the DBIx::Class ORM and the Moose metaprotocol and object system, as well as contributing to assorted other CPAN projects.
Matt spends his days leading the technical team at Shadowcat Systems Limited, an open source consultancy specialising in Catalyst, Perl applications deployment and systems architecture. Shadowcat sponsors web, source repository and mailing list hosting for Catalyst, DBIx::Class and a large number of associated projects, and creates and releases open source code both internally and on behalf of its clients.
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at email@example.com
Download the OSCON Sponsor/Exhibitor Prospectus
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the OSCON Newsletter (login required)
Have an idea for OSCON to share? email@example.com
View a complete list of OSCON contacts