Pre-release testing

Stewart Brodie stewart at eh.org
Fri Apr 14 10:08:31 BST 2000


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.

-- 
Stewart Brodie, Senior Software Engineer    (Views expressed are my own and
Pace Micro Technology PLC                   not those of my employer)
645 Newmarket Road
Cambridge, CB5 8PB, United Kingdom         WWW: http://www.pacemicro.com/



More information about the oslib-team mailing list