On Wed Nov 26 13:18:57 2008, coke wrote: > > > The only remaining instance in branch that I'm not sure how to resolve > is > > t/configure/034-step.t > > Jim - if you could take a look at that usage of miniparrot and either > bless it or remove it, that'd be very helpful. (I can't tell if it's > referencing the executable or the config option.) >
It was just dummy copy. The point of that particular test was to see if genfile() caught the Perl error found in 'sprint' in the next line. But I changed it anyway so that grep wouldn't find it -- and added a test for the captured error message while I was stopping by. I was mistakenly working in trunk rather than branch today when I updated 5 t/steps/*.t test files. I then subsequently discovered that you worked on those files yourself today in branch. So you might get some trivial conflicts when you do the merge. Coverage analysis for configure and build tools in the rm_miniparrot branch can be seen at http://thenceforward.net/parrot/coverage/configure-build/coverage.html. AFAICT you can do the merge back into trunk whenever you're ready. Thank you very much. kid51
