Dear Monks
it's never been quite clear to me how to get full -E behavior with a stdin script. Let's call perl from a shell script (this the reason for not wanting -E, and some other choices):
perl -Mv5.12 -wn -- - /etc/passwd <<'EOF'
next unless / ([^:]*) : [^:]* : ([0-9]+) /x;
my ($w, $n) = (uc $1, 5000 + $2);
say qq{log=$w id=$n}
EOF
As I understand it, -E turns on optionals (e.g. say, <<>>), but also some behaviors (e.g. use strict, Unicode handling). Now the unpalatable choices become
- specify a "minimal minimum" version (e.g. -Mv.5.12) to get say and strict; but that probably disables post-5.12 changes
- specify a "maximal minimum" version (e.g. -Mv5.28), but that fails for older Perls
- use -E with an inline single- / double-quoted shell string, with all the niceties of shell quoting / escaping
- use -E with a wastefull -E "$(cat <<"EOF" ... )"
Are there any other options to get -E behavior without -E?
-
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
or How to display code and escape characters
are good places to start.
|