Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

Re^3: Restarting a Perl script on Windows 10

by stevieb (Canon)
on Sep 20, 2019 at 23:11 UTC ( [id://11106457]=note: print w/replies, xml ) Need Help??


in reply to Re^2: Restarting a Perl script on Windows 10
in thread Restarting a Perl script on Windows 10

"Really the best answer is probably to get a better operating system..."

As nice as that sounds, there are all number of reasons why this may not be desirable, feasible, or even possible for some people.

Personally, the only time I use Windows is when I'm developing berrybrew. I've got a few VMs configured for that. So realistically, I only use Windows to develop software that I don't even use :)

...that's not entirely accurate. I use my Test::BrewBuild CI automation against Perl instances running under berrybrew on a Windows system that all it does is listen for incoming test run requests. I have a VM set up with Perlbrew as well for the exact same purpose. All of my distributions (the cross-platform ones) are automatically tested against both Windows and Unix over the network, across at least 10 versions of Perl before I do a CPAN release.

Replies are listed 'Best First'.
Re^4: Restarting a Perl script on Windows 10
by jcb (Parson) on Sep 21, 2019 at 23:49 UTC

    I understand some people may be stuck with Windows for whatever reason (and I have used it at $WORK because that is what someone else decided $WORK would use) but the issue at hand is breakage after an OS update for which workarounds may be possible but are definitely non-portable. Perhaps the Perl 5 porters could include something functionally similar to one of my suggestions in the implementation of exec on Windows Perl for Windows 10? But Windows no longer really has versions anymore, only "Windows 10 rolling release with mandatory automatic updates" so how to determine when to use the workaround and when to use the traditional code that worked before?

    Working around Windows' brokenness is still working around Windows' brokenness, which you cannot fix because you are not Microsoft, so the best solution is to move to a non-broken operating system, or at least to a system you can fix. I suggest GNU; avoiding these kinds of problems was a significant motivation for the GNU project, as I understand it.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11106457]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (3)
As of 2024-04-25 12:55 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found