On Mon Dec 17 06:30:45 2007, particle wrote: > > > i see that as of r23980 (and beyond) you've moved these subs into a new > module Parrot::Configure::Compiler, converted them to methods, and made > the module a superclass of Parrot::Configure. this seems sane. carry on. > ~jerry
Yes, I got it passing all tests on Darwin this morning but need to update the docs appropriately. I'll probably also propose renaming Parrot::Configure::Step to something like Parrot::Configure::Compiler::Utils to better reflect what its remaining subroutines are doing. That will enable us to also rename Parrot::Configure::Step::Base to Parrot::Configure::Step -- which will mean that Step.pm will finally do what its name leads you to expect it will do, namely, provide a constructor for a Parrot configure step class. All this should be ready for presentation to trunk in a couple of days. Thanks for reviewing. kid51
