Still, while I mostly prefer python to perl too these days, we have to
consider that perl is already a pre-requisite for projects using autoconf,
automake, and/or gnulib, so using perl would have the advantage of not
adding another requirement to the maintainer toolchain.
Certainly. I am not a big fan of Perl, but it is already a requirement
for automake. To introduce yet another interpreted language into the
chain would be very annoying.
Two caveats though, if we go down this road:
- We should be careful not to over-engineer, especially in the earlier
phases.
Yes please. The logic involved in running a set of mostly independent
tests, either sequentially or in parallel probably does not merit the
usage of elaborated object orientation artifacts such as classes.
Lets keep it easy to read, easy to understand and easy to hack, please.
Just my 2 cents.
--
Jose E. Marchesi jema...@gnu.org
GNU Project http://www.gnu.org
