G'day Discipulus,
Firstly, sorry for the late response.
I had some fairly major dental work last week:
I've spent the last few days recovering and doing little else.
Thanks for the script and examples.
I imagine that code could be put into a module; perhaps used something (very roughly) like:
...
use if $^O eq 'MSWin32', Win32::Exit::Prompt => 'exit_prompt';
...
exit_prompt() if $^O eq 'MSWin32';
exit;
That's still extra code for every script and, as you say, it "is slow".
As running Perl scripts directly from Win10, instead of from Cygwin, is likely to be an infrequent requirement for a $work task
— at least for the time being — I'll probably be looking at handling this in the following order:
-
Run scripts without extra code from cmd.exe
(see discussion under VinsWorldcom's response).
-
Run scripts without extra code from a possibly reconfigured PowerShell
(see discussion under Orangutan's reply).
-
Run scripts with your extra code from anywhere.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.