The experiments and deprecation regime for perl core has changed significantly over the years which is a great thing. I'm wondering if it has been considered to create a new CLI flag to determine within files whether either one are being used without exercising the code (like the -c flag for syntax).
I thought about writing a Test:: module for this, but after only about 15 minutes, realized that it would be nearly futile without both very excessive build prereqs and nearly impossible-to-keep-updated trickery. I do think it would be a nice feature to have, to be able to throw a list of files at perl blead and see if any of one's modules within it may require changes before the next public release without having to actually ensure 100% test coverage, and rebuilding/testing all your modules/scripts prior to each one.
Is this something reasonable, or am I over-thinking again?Update: for those who aren't aware, perl blead is the most recent build of core perl's development code, always in an odd version number. Currently, blead is 5.23, in prep for the public release of 5.24. blead == trunk/master etc.
In reply to Could perl have a "do these files contain experimental/deprecated features" flag? by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |