On 7 September 2016 at 11:37, Corey Huinker <corey.huinker@gmail.com> wrote: > On Tue, Sep 6, 2016 at 11:24 PM, Craig Ringer <craig.ringer@2ndquadrant.com> > wrote: >> >> On 7 September 2016 at 11:21, Corey Huinker <corey.huinker@gmail.com> >> wrote: >> > On Tue, Sep 6, 2016 at 6:53 PM, Craig Ringer >> > <craig.ringer@2ndquadrant.com> >> >> > And the TAP test would detect the operating system and know to create an >> > FDW >> > that has the PROGRAM value 'cat test_data.csv' on Unix, 'type >> > test_data.csv' >> > on windows, and 'type test_data.csv;1' on VMS? >> >> Right. Or just "perl emit_test_data.pl" that works for all of them, >> since TAP is perl so you can safely assume you have Perl. > > > Thanks. I was mentally locked in more basic OS commands. Am I right in > thinking perl is about the *only* OS command you can be sure is on every > architecture?
Probably, there's a lot of crazy out there.
TAP tests can be conditionally run based on architecture, but something like this is probably worth testing as widely as possible.
I'm inclined to go inline to cut down on the number of moving parts, but I can see where perl's readability is a barrier to some, and either way I want to follow established patterns.
