The problem is that Win32's "echo" preserves the quotes and so is poorly suited for this task: 

C:\>echo "print qq(Hello.\n)"
"print qq(Hello.\n)"

[download]
vs. 
$ echo "print qq(Hello.\n)"
print qq(Hello.\n)

[download]
so you get the equivalent of perl -e "\"print qq(Hello.\n)\"" instead of perl -e "print qq(Hello.\n)" So piping other things to perl works fine in Win32 (so find2perl shouldn't be a problem -- I used it quite recently).

        - tye (but my friends call me "Tye")

In reply to (tye)Re: piping commands to perl via standard input on the Win32 command line by tye
in thread piping commands to perl via standard input on the Win32 command line by frag

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.