A topic that can easily make anyone’s mind wobble. Here I try to make them stick in to your mind (and maybe mine) by explaining them in the simplest way possible.
- The C Book
- C Elements of Style
- Build Your Own Lisp
- The GNU C Reference Manual
- The GNU C Programming Tutorial
- Essential C
- Beej’s Guide to C Programming
- Modern C
- An Introduction to GCC
This post will provide a brief hands-on introduction to ORM in Perl using a few DBIx::Class sub classes.
In detail, this means we will generate Schema, Result and ResultSet classes (Perl modules) which will be used to interface with a SQLite database. The database will contain a single users table. Once the database has been created, we will implement functionality to both return the full name of a user, and find all users under a given age. To ensure the functionality of the schema, this code will be implemented using Test Driven Development (TDD), where the tests will be written first, then made to pass as we add new functionality.
This article is divided into two parts. The first part is doing the groundwork — installing Perl modules, setting up the directory structure, the database to test against, and a unit test against which we can measure our progress. In the second part we will create a database and use DBIx::Class modules to make the tests pass.
part 1 — installing Perl modules, setting up the directory structure, the database to test against, and a unit test against which we can measure our progress.
part 2 — creating a database and using DBIx::Class modules to make the tests pass.
My conclusion is that you should write an emulator for any service you are developing against. Not just that but release an emulator for any RESTful APIs you are developing for others so they can trivially test their client code.
Having done the emulation dance for at least three modules I’ve written I suggested I would write something to make this easier. I managed to find some time last week to do this.
Over the years we’ve added quite a bit of stuff to GitHub. Sometimes we ship huge features, sometimes we ship small, lesser-known bonus features.
Let’s talk about some of those secret features you may not know about.
Most of our codes [sic] are not perfect in many ways and it will take ages to list all the possible flaws. However, I will list some of the most common and frequent mistakes and give some suggestions to fix them.
This is the first post of a series on the Mojolicous web framework originating from my experiences at ISP, Fachbereich Informatik of the Technische Universität Darmstadt. Step by step, we will create a simple blogging platform using Mojolicious.
Only 7/12 parts completed