[Gzz] 22nd

[B. Fallenstein]

1. Wrote the URN informal namespace application I proposed earlier; it's 
at Documentation/misc/urn-application.txt. One thing has changed: cells 
have the form urn:urn-n:abcdefghiklmnopqrstuvwxyz:2, not 
urn:urn-n:abcdefghiklmnopqrstuvwxyz#2, because the # is reserved in the 
URN syntax. (Strange... no fragments of URN-identified documents? 
Anyway.) The application is supposed to be submitted tomorrow (23rd).

2. Started a Python script to make test writing easier 
(test/testutil.py). This allows you to create a simple .test script and 
put it into the test/ tree-- testutil will run it as a 
unittest.TestCase. It's not yet incorporated into test.py (because so 
far, there is only a demo using it), but you can try by running 'jython 
test/testutil.py' in gzz/. (You can use python instead of jython for 
performance.)

After you've run testutil, look at test/demo.test.

testutil is by no means finished. It does work, but it doesn't make the 
common tasks of test writing easy enough. This will come with practice-- 
it's good enough to start using it and have an easier life than with 
unittest, but for example abstract tests ("any dimension must pass 
this") need changes to testutil (esp. if we want them to be really 
simple to write).

The idea behind this is that tests should be *really* simple to write. 
You shouldn't have to write a lot of headers and 'self.'s and make 
changes to the test suite hierarchy to get your tests to run. It should 
be like, create a new file, write a few lines (the minimum amount to get 
anything run), see whether your code works, write a few more lines, and 
so on-- test writing should be fun, not effort.

-b.