Nope, not a lot of dev work at all. After following Limbic~Region's advice, I got to see the code (by joining pmdev). After about 10 minutes of searching and looking around, I figured out at a conceptual level what I would need to do, and I figured it would end up being about 5 lines of code added, and perhaps a couple lines changed. That's the easy part.

Next on the agenda is to do it and test it, then submit it. Discussions may break out anew, wars started, people killed. That doesn't concern me. I need to figure out how to test it. Nothing is worse than submitting an untested patch :-) The few CPAN modules I've submitted patches to have always been tested prior to even asking questions about them, let alone submitting them. I don't want to change that habit - at least, not quite yet. :-)

I'm hoping a few more minutes of searching will reveal how this is done, but that'll have to be done later, I've run out of time for this right now.

PS - so far, all the code I've looked at has been quite good. The only differences between how I code and how the code is written are in generally accepted contentious styles (e.g., "one-true-brace-style" vs other placements of bracing). Absolutely nothing has grated on me, so I'm quite impressed. :-)