WinDOS uses the DOS model and does not pass arguments to invoked processes, only a "command tail" string that all Windows C runtime libraries parse into argc and argv using some rules or other.

Using wperl as in your example means that $pathToMyself is already being passed as the "command tail" to wperl. Try:

my $argtail = join ' ', @args;
exec(qw/wmic process call create/ => "CommandLine='wperl $pathToMyself
+ $argtail'");

[download]

If you are wondering, yes, this does mean that arguments containing whitespace are a problem. Quoting is handled by C runtime library startup code and that can vary from program to program because there is no standard system C runtime library on Windows.

In reply to Re^4: Restarting a Perl script on Windows 10 by jcb
in thread Restarting a Perl script on Windows 10 by petro4213

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.