Here's a version that's not quite so funky (but still kinda ugly). This is a situation in which a prototype is actually useful. If the  hiccup() function is defined in the source file in which it's used | invoked, either the full definition of the function or a prototype declaration must appear before first invocation of the function. If the function is moved to a module, a use statement must appear before first invocation.

File hiccup_here_3.pl:

use warnings;
use strict;

use Hic;
# sub hiccup (&@);

my $lanCidr = 'WHATEVER';
my $dmzIp   = 'SOMEWHERE';
my %ipAddress = qw(HERE we_are  THERE it_goes  EVERYWHERE at_once);
my @array     = qw(WIBBLE BOFF);

my $s = << "EOF";
iptables -t nat -N outbound-DMZ
@{[ hiccup {
    "iptables -t nat -s $lanCidr -o $_ -j SNAT --to-source $dmzIp"
    } keys %ipAddress ]}
whatever else here
@{[ hiccup {
    "flocculate -f $_ -j SNAT --to-source $dmzIp"
    } @array ]}
iptables -t nat -A outbound-DMZ -j RETURN
EOF

# sub hiccup (&@) { return join "\n", map $_[0]->(), @_[ 1 .. $#_ ]; }

print "[[$s]]";
[download]

Module Hic.pm:

package Hic;

use warnings;
use strict;

use parent 'Exporter';

our $VERSION = '0.1.0';

our @EXPORT    = qw(hiccup);  # default exported symbol(s)
our @EXPORT_OK = qw();        # optional exported symbol(s) (none)

sub hiccup (&@) { return join "\n", map $_[0]->(), @_[ 1 .. $#_ ]; }

1;
[download]

However it's invoked, the function produces the following output:

c:\@Work\Perl\monks\Anonymous Monk\1197277>perl hiccup_here_3.pl
[[iptables -t nat -N outbound-DMZ
iptables -t nat -s WHATEVER -o EVERYWHERE -j SNAT --to-source SOMEWHER
+E
iptables -t nat -s WHATEVER -o THERE -j SNAT --to-source SOMEWHERE
iptables -t nat -s WHATEVER -o HERE -j SNAT --to-source SOMEWHERE
whatever else here
flocculate -f WIBBLE -j SNAT --to-source SOMEWHERE
flocculate -f BOFF -j SNAT --to-source SOMEWHERE
iptables -t nat -A outbound-DMZ -j RETURN
]]
[download]

Update: Screwed up initial post of hiccup_here_3.pl file. Fixed.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.