The problems discussed in the reports presented here are necessarily miscellaneous. Their only reason for selection is their occurrence, typically with nuisance value, in an ordinary working life when there happened to be sufficient spare time and interest both to investigate the problem and to prepare a report. (The study is relatively easy: it is the writing-up that is hard.)
As all programmers are only too well aware, many problems with software are caused by strikingly simple coding errors. The good news for users, who do not have the source code to edit, is that knowledge of a simple coding error often leads to one of two ways to deal with it independently of the manufacturer. One is to work around the coding error by operating the program in a slightly different way either to avoid executing the faulty instructions or to compensate for them. The other is to repair the faulty instructions by patching the executable.
Each problem report below is titled as if the problem’s occurrence is given. This style tends to produce shorter titles. Its use is not intended to suggest that the stated problem occurs in all circumstances.
For each report, the dates given in brackets after the title are respectively the dates of creation and of last significant modification.
Copyright © 1997-2004. Geoff Chappell. All rights reserved.
[Home][Programming Samples][Application Notes][Security Notes][Editorial][Consultation][Contacts]