Pre-release testing

[Tony van der Hoff]

On Fri, 14 Apr 2000, at 10:08:31, Stewart Brodie <stewart at eh.org> wrote
on the subject "Pre-release testing":

>I suggest that somebody builds a simple file that just #includes every single
>OSLib header file to make sure you don't get compilation warnings or errors
>at that phase, and have the test file go on to attempt a declaration of each
>type provided by the library.  Now obviously, this would have to be
>automatically generated - unless we have any masochists here - but would
>hopefully prevent the problem with OSLib 6.00.
>

Thanks, Stewart. If you look in the oslib.Source.Test directory, you'll
find just such a file, initially created by Jonathan, and updated by
myself. However, the second part of your proposal would be a good
enhancement, but as you say, not one for manual implementation.

Could DefMod be persuaded to provide such a test?

Confession time:
I had successfully compiled Test.c for the 6.00 alpha release. It did
show up lots of problems during development and was thus extremely
valuable.  Unfortunately, I forgot to re-compile it for 6.00 beta after
I renamed |_W| to |W| (and missed one).  It would have - and
subsequently did - pick that up.

It also only tested the development version of the library, not the
published version, so it did not pick up the lack of Macros.h and
types.h in the include path. I fixed that omission for 6.01.

All this just goes to show that you can have all the tools in the world,
but still rely on some human to cock it up - in this case me :-(

It did not - and could not - pick up the errors generated by the Defmod
bug, presumably your proposed enhanced version would have done.

-- 
Tony van der Hoff         |  Mailto:tony at mk-net.demon.co.uk
                          |  Mailto:avanderhoff at iee.org
Buckinghamshire, England  |  http:www.mk-net.demon.co.uk