Ricardo Signes wrote:
I would like to refactor the code as I work so that methods are easier to find, use, and replace as needed. Maybe I can fill in some of the "to do" documentation, once I understand what the hell is going on. Is anyone going to be put off by these kinds of changes *in general*? The first one I hope to make is to add $self->debug($level, $msg) to replace the use of "print" which is broken when there's a non-STDOUT handle select-ed. That's also a good taste of the kind of changes I think I'll end up wanting to make.
Full approval from me. The way I inherited Pod::Simple in the first place was because I kept sending Sean patches to refactor the internals while I was developing Pod::PseudoPod. My one caution is to be very careful about changing the interface, as there are several other core modules that depend on it. And because of Pod::Simple's limitations in the subclassing department, many subclasses have had to poke into the internals to get things to work, so the "interface" includes some pieces that might seem strictly private at first glance.
As a bonus, now that David has kindly moved the Pod::Simple repository to Git, it's quite easy to fork, work, and merge.
Allison
