Andy Dougherty wrote:
(If cc_build and cc_run do get
meaningful exit codes, inter::progs needs to be revisited anyway to
actually use those codes.)
If you do revisit config/inter/progs.pm, please bear in mind that I have
written some unit tests for that package:
[parrot] 500 $ ls t/configure/*progs* | cat
t/configure/107-inter_progs.01.t
t/configure/107-inter_progs.02.t
t/configure/107-inter_progs.03.t
t/configure/107-inter_progs.04.t
The extent to which these tests cover the code in the package can be
seen here:
http://thenceforward.net/parrot/coverage/configure-build/config-inter-progs-pm.html
So if you start refactoring, please make that a test-driven process so
that we keep the code coverage high. I'll be happy to point out any
pitfalls.
Thank you very much.
kid51
