-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey all,
I've been working on converting the CVS test suite (of CVS itself) to
use Autotest, and after converting the first few hundred lines of tests,
it is starting to look like the final version of the Autotest generated
test suite will be upwards of 20MB in size.
I plan on optimizing a few things I did in the CVS test suite, but I
think that will prove the difference, at best, between 25MB and 20 MB.
Does anyone have any thoughts on how the size could be reduced? Perhaps
there is room for optimization in some of the Autotest macros?
One of the other CVS developers and I were discussing putting some of
the test setup we reuse with almost every test in shell functions, but I
know that the Autoconf manual is pretty adamant about not including
shell functions in portable shell. How many systems will we lose if we
start using shell functions?
Derek
- --
*8^)
Email: derek@xxxxxxxxxxx
Get CVS support at <http://ximbiot.com>!
- --
Nobody likes sunburn slappers.
Nobody likes sunburn slappers.
Nobody likes sunburn slappers...
- Bart Simpson on chalkboard, _The Simpsons_
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
iD8DBQE/uPSwLD1OTBfyMaQRAowMAKD9tBdhFs85JobuqMOSLg5Zjdy5nACfYMZ+
nTWm3eux70NGQFYQh9jMQs0=
=fr3b
-----END PGP SIGNATURE-----
|
