Re: [PATCH] ecrypto/blowfish.el integer constant fix

Simon> The only bad about it I can see is that it takes away time Simon> from more important things, There is nothing more important than testing. Among other things, there are a number of areas where the best documentation we have for certain counter-intuitive (to me, anyway) functionality is a test case explicitly written to make sure XEmacs works that way. It's also a good way to get bugs fixed. I put some tests in, the Voice of Dog (that's God in Australian, which, if not backwards, is upside-down) said "THERE WILL BE NO RELEASE UNTIL THOU SHALT REPENT OF ALL TEST FAILURES," and by golly, the tests failures miraculously disappeared (and not because the tests were disabled, either!) Simon> FWIW, when I suggested a test suite for Emacs to RMS Simon> several years ago he didn't like it either, because he felt Simon> that emacs went through a self-test during bootstrap. That's not surprising. rms doesn't believe in engineering. He's a hacker to the bone. But he's just plain wrong, at least if you have Ben Wing and Mike Sperber keeping things stirred up. Having the test suite to keep us honest has helped us return to stability more quickly after several big changes, in my somewhat informed opinion. Now, if I can come up with some tests for specifier behavior and Crushtomize.... -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.