comment on

Something like this works:

sub IFACE {
  my $pattern = shift @_;
  my $result;
  foreach $iface (@_) {
    $result .= (eval "\"$pattern\"") . "\n";
  }
  chomp $result;
  return $result;
}

&utter( <<"EOF" );
iptables -t nat -N outbound-DMZ
@{[ &IFACE(
  "iptables -t nat -A outbound-DMZ -s $lanCidr -o \$iface -j SNAT --to
+-source $dmzIp",
(keys %ipAddress)) ]}
iptables -t nat -A outbound-DMZ -j RETURN
EOF
[download]

I know it's unconventional but I've capitalised the function name to emphasise its relationship to the name of the variable being interpolated, I felt that trying to pass that name as a parameter would be pushing my luck. It's (obviously) very sensitive to the double-quotes being correct, both in the function and in the heredoc itself. The one thing I wasn't able to get working was ~ to enable indents (5.20.2 on Debian Jessie armhf), but that's a fairly detail since the nearer the heredoc is to the actual stuff going into the tables the better.

Many thanks to everybody, especially NetWallah.

Pax vobiscum, MarkMLl

In reply to Re^2: hiccoughing here documents by Anonymous Monk
in thread hiccoughing here documents by Anonymous Monk

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.


Problems? Is your data what you think it is?
	PerlMonks