Just as a side note, I've been using unit testing for my projects and it works really nicely. You test certain conditions on a function or method and depending on the outcome pass or fail. Note thatyou can create unit tests that cause a failed condition to occur and that i itself is passing. The good thing about it is when you've a full set of unit tests for a library, you can continue work on the library or code and not worry that the part you're working on broke something else- or if you did, you might find out about it sooner. L On Sat, 16 Nov 2002, Matthijs Hollemans wrote: > > > > >1) Testing > > > > In fact I test it but not with a special test unit I compile > > the same app with libmidi and with the source I write, > > if the answer are same I suppose it's OK. > > Well, that is very good, of course. But we still need unit tests for > the classes. And trust me, it is easier to write them now than > later. (Actually, the best way is to write the tests before you > write the real code.) > > Thank you for the images, by the way. I suppose you want me to put > them on the MIDI website? > -- > Matthijs > > > >