You can cd to lib/unicore and run 'make test', and mktables will generate a test file and attempt to run it. It doesn't currently work very well. In my attempts to clean up mktables, I have a version that creates a working test script. It turns out that t/uni/class.t uses much the same algorithm for generating most of its tests, and it will need to be heavily revised. So I was wondering is it an ok idea to replace the testing that class.t does by the improved file that mktables generates? If so, should it be a .t, and installed into the t subdirectory, or can somehow make test at the higher level call the one in unicore?Thread Next