On Mon, Feb 13, 2017 at 3:22 PM, Neil Bowers <neil.bow...@cogendo.com> wrote:
> The pair of VMS::stdio and VMS::Stdio is a bit more tricky: > > ext/VMS-Stdio/Stdio.pm starts with the expected: > > package VMS::Stdio; > > > but then later on we see: > > > ################################################################################ > # Intercept calls to old VMS::stdio package, complain, and hand off > # This will be removed in a future version of VMS::Stdio > > package VMS::stdio; > > > If you look in the CPAN index (02packages), you’ll see that it’s the > deprecated VMS::stdio that gets indexed. > > Questions: Are we enough in the future that VMS::stdio can be dropped? And > more relevantly for me, am I ok to drop all the permissions on VMS::stdio? > That would result in VMS::Stdio being indexed for the next release, though I > don’t think the indexing is that much of an issue, since they’re core > modules with upstream undef. Yes to both those questions. I think twenty-one years is enough: <https://perl5.git.perl.org/perl.git/blobdiff/5ba038830444bcc101e0d58356269b7057fa892d..0d7e20a5efe3be79041a6ea959eb46b964c2e4da:/vms/ext/Stdio/Stdio.pm>
