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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|