Back in February, I asked: >> 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. >
Craig said: > Yes to both those questions. The attached patch drops the VMS::stdio shim, so there will just be VMS::Stdio. The latter had doc that talked about the compatibility shim, so I changed that doc to say that the VMS::compatibility shim has been dropped. Background Perl 5 initially shipped with VMS::stdio. In 5.002 this was changed to VMS::Stdio, but that has included a cuckoo package for VMS::stdio, which used AUTOLOAD to generate a warning if you used VMS::stdio, then redirect calls to VMS::Stdio. 5.002 was quite a while ago now, so we’re dropping the compatibility interface. I’m doing this so we don’t have conflicting package names when PAUSE consider package permissions. Cheers, Neil
0001-Drop-VMS-stdio-compatibility-shim.patch
Description: Binary data
