We've discussed several times on this list the removal of Pod::Parser from the core, as it's poorly understood and mostly abandoned for new Pod-handling code. This summer, Marc Green did an admirable job of converting some of our core Pod-handling code to use Pod::Simple, bringing us nearly to a state where we can begin to seriously consider removing Pod::Parser. These tasks remain: 1. complete the conversion of Pod::Checker and podchecker code to Simple 2. deal with Pod::Usage 3. deal with Pod::LaTeX 4. mark Pod::Parser deprecated 5. remove Pod::Parser from the core At present, it seems unlikely to me that we will have 1-3 complete in the next few weeks to hit 4 by the contentious code freeze. Is deprecating Pod::Parser contentious? I doubt it, but stranger things have been argued over. At any rate, even if this does not land for 5.16, I'd like to keep movement going on it. (1) clearly has to finish. The podchecker test is very important. For (2), I think Pod::Usage should be entirely converted to Pod::Simple. It already uses Pod::Simple and Pod::Parser both, in strange ways. If we're all very lucky, maybe Marc will feel excited by the proespect of doing more of this work. (3): I spoke with Tim Jenness, the current maintainer of Pod::LaTeX, and I think the correct course of action is to deprecate Pod::LaTeX for removal along with Pod::Parser. It is not likely to see any compatible conversion to Pod::Simple, and is not in my opinion a vital part of the core library. Once those are done, we're safe to also deprecate Pod::Parser. -- rjbsThread Next