Pre-release testing

[Jonathan Coxhead]

 | 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,

   See examples.c.test for (an out-of-date) one of those.

 | and have the test file go on to attempt a declaration of each type
 | provided by the library.

   It doesn't go that far, though.

 | 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.

   Clearly, we have *many* masochists here! :-)

   When I was the maintainer, at each release I used to check that 
all the examples compiled (c.test was the best one), and that any 
differences between the s files aand h files as generated by the 
previous version were for reasons I clearly understood (regression 
testing). I also made sure that whatever programme I was working on 
at the time still worked, to give a bit of confidence about run-time 
behaviour.

        /|
 o o o (_|/
        /|
       (_/