CVu V16 2 PDF

Rather than talk about programming or programming issues, the work of WG21 etc, I've decided to talk about something far closer to my heart; the state of computer programming courses in education at all levels.

Recently, I've been thinking hard about what makes code maintainable, and how to write code to be maintainable. This interest has partly been driven by the mentoring of those starting out in C++ that I've been doing, both through the ACCU mentored developers program, and for work.

The principles I've identified have not really been hidden; since they've been widely documented for years, and they're actually things that most good developers do as a matter of course. However, as with many things, you don't necessarily realize their benefits until you rediscover them yourself.

Please note that participation in this competition is open to all members. The title reflects the fact that the code used is normally provided by a student as part of their course work.

This item is part of the Dialogue section of C Vu, which is intended to designate it as an item where reader interaction is particularly important. Readers' comments and criticisms of published entries are always welcome.

In the first part of this series, we looked at what it means to optimise code, and saw the cases for and against optimisation. In this article, we'll look at the process of optimisation. We'll see the correct, methodical approach that will lead to solid, worthwhile code optimisations.

This is the second of a two part article describing an experiment carried out during the 2003 ACCU conference. The first part was published in a previous issue of C Vu (15.6, December 2003) and discussed the background to the experiment and some of the applicable characteristics of the subjects taking part; this one, the second, discusses the results of the experiment.

Look at the following code and decide what is wrong with it. When you have done so, decide what it has to do with the previous section in particular and this section of C Vu in general - well actually the whole of your life.

There have been many languages for writing applications, but relatively few foundation platforms which support applications that are written in various different languages. We've had assembler (proprietary), then C (an ISO standard), and now we have the Common Language Infrastructure (CLI). The CLI standard is ISO/IEC 23271; the same content is also available online at http://www.ecma-international.org/publications/standards/Ecma-335.htm.