<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Sep 8, 2016 at 6:59 PM, Craig Ringer <span
dir="ltr"><<ahref="mailto:craig.ringer@2ndquadrant.com" target="_blank">craig.ringer@2ndquadrant.com</a>></span>
wrote:<br/><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class=""><pdir="ltr"><p dir="ltr">On 9 Sep. 2016 03:45, "Corey Huinker" <<a href="mailto:corey.huinker@gmail.com"
target="_blank">corey.huinker@gmail.com</a>>wrote:<br /> ><br /> > <p dir="ltr">> Stylistically, would a
separate.pl file for the emitter be preferable to something inline like<br /> ><br /> >> perl -e 'print
"a\tb\tcc\t4\n";print "b\tc\tdd\t5\n"'</span><p dir="ltr">I'd be fine with that and a suitable comment. Just be careful
withdifferent platforms' shell escaping rules.</blockquote></div>Do perl command switches on windows/VMS use /e instead
of-e? If so, that'd be a great argument doing just "perl filename".</div><div class="gmail_extra"><br /></div></div>