comment on

perl -le "open(my $x, "">&STDOUT"");"

Not quite - but close enough ;-)
Thank you.
Either of the following work and, AFAICT, are equivalent - though I'm not exactly sure why that equivalence should hold:

perl -le "open(my $x, \"">&STDOUT"\");"
perl -le "open(my $x, "\">&STDOUT\"");"
[download]

So I gather it's just the way the shell functions (as opposed to an issue with perl), that I can do:

C:\_32>perl -Mstrict -MDevel::Peek -le "my $arg = \"STDOUT\"; Dump $ar
+g;"

SV = PV(0x36cd1c) at 0x44b124
  REFCNT = 1
  FLAGS = (POK,IsCOW,pPOK)
  PV = 0x451dc4 "STDOUT"\0
  CUR = 6
  LEN = 10
  COW_REFCNT = 1
[download]

but it blows up as soon as I introduce shell metacharacters into the string:

C:\_32>perl -Mstrict -MDevel::Peek -le "my $arg = \">&STDOUT\"; Dump $
+arg;"
>& was unexpected at this time.
[download]

And I guess the additional quotes provide the disambiguation required to allow the one-liner to DWIM.

Cheers,
Rob

In reply to Re^2: [Win32] Escaping quotes in perl one liner by syphilis
in thread [Win32] Escaping quotes in perl one liner by syphilis

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.


laziness, impatience, and hubris
	PerlMonks