Every so often I come across the question "should we use return codes or exceptions to report errors."

It is possible to apply OO techniques to make better C programs and that is the thrust of this article.

I sometimes find that algorithms are like buses. I spend ages looking for a good algorithm to solve a problem, and then two come along at once.

This article is based on an overview that I wrote to help introduce developers on a pilot project to unit testing. It covers the strategic reasons for using unit tests and the tactics of writing a unit test harness using the freely available JUnit framework to minimise the work involved.