+1 on CVS +1 on mailing list +1 on JUnit -- While creating the patches, the tests found several mistakes I made. This is very important. +1 on the fewest obstacles to commiting patches to CVS. If this means meritocracy, then I am for it. I think that preventing someone from contributing will hurt our project.
On another note... I submitted several patches to fix multithreading issues and I would like to make some JUnit tests, but I do not see how. Can anyone suggest a way to test a multithreaded bug? For example, Trace.java has a static variable called iStop. If there are multiple databases running, then Database.execute() will allow 1 thread per Database to pass through, so you could have multiple threads in Database.java and also Trace.java. If the two threads hit "iStop++;" at the same time, then there could be a problem. How do you create a test to detect something like this? I am for having a single threaded core for this reason. It is difficult to write JUnit tests for multithreaded applications. With a single threaded core and JUnit, we can submit patches that have fewer bugs and hsqldb will be higher quality. -Clay _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
