Forwarded to list pending return to life of rt.perl.org:
According to its documentation, the purpose of
Parrot::Configure::Step is to hold "... utility functions for
[configuration] steps to use."
This package, in relation to others in the Parrot::Configure::*
tree, has a relatively large amount of code not covered by tests in
t/configure/ or elsewhere. (See http://thenceforward.net/parrot/
coverage/configure-build/lib-Parrot-Configure-Step-pm.html.)
Additional unit tests are needed to deal with 3 aspects of this
package:
1. prompt(): As yet not covered by any unit tests. Whoever works
on this should see whether this subroutine is called anywhere in
the lib/ or config/ hierarchies.
2. Branches and conditions in various subroutines: file_checksum
(); genfile(); run_command(); cc_build(); cc_run(); cc_run_capture
(); check_progs(); slurp(). As with item (1), each subroutine
should be checked for current instances of usage during configuration.
3. There has been talk in other RT threads cc_build() a
"meaningful return value" (cf. http://tinyurl.com/2e7glm).
So this is a 3-part task involving testing and possibly refactoring.
kid51
