The stupid question is the question not asked | |
PerlMonks |
Re: Perl and MSWin11: any issues?by Discipulus (Canon) |
on Sep 09, 2021 at 11:26 UTC ( [id://11136608]=note: print w/replies, xml ) | Need Help?? |
Hello kcott, if you accept my precognition.. I bet you have not to expect any issue. My point of view is: according to this cnet serie of articles they are betting on hyper-high-level integration with mobile devices and they as always will not touch the under hood ecosystem. Our work in Perl on Windows is at a level they probably will never touch. Fewer Win32::* XS modules we have on CPAN that interact directly with internal system calls survived since the WindowsNT era and they still works because the underlying OS component never changed. Microsft OSs still supports ancient things like CLSID: EXPLORER ::{2227A280-3AEA-1069-A2DE-08002B30309D} (to open printers) never stopped working across versions. The major mess they introduced over ages is the 32bit vs 64bit madness and the confusing path names and subtle filesystem redirection.. but we already survived to this. Following in the realm of precognition, you can face minor issues in highly OS integrated fields like Task Scheduler or Services, so if you write Windows services in Perl (congratulations!) you must double check them on a newer OS. But, again, I still use year 2k code to parse events in Event Viewer and never faced "newer" problems: always same old ones :) Anyway I'd really appreciate if you update this node as you find something related.
L*
There are no rules, there are no thumbs.. Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
In Section
Seekers of Perl Wisdom
|
|