Kevin Grittner wrote:
> I find the TestLib.pm framework to be more friendly with the
> attached tweak to SimpleTee.pm.
Pushed.
Please ignore the typo in the commit message -- I was looking right
at the code saying "autoflush", but what came off my fingers (from
muscle memory?) was "autocommit".
Kevin Grittner writes:
> Tom Lane wrote:
>> Just out of curiosity --- what's the rationale for flushing after
>> every line, rather than once at the end of the loop?
> Isn't the loop over file handles written to?
Oh... I just automatically read it as looping over some data,
not printing the sam
Tom Lane wrote:
> Just out of curiosity --- what's the rationale for flushing after
> every line, rather than once at the end of the loop? Is there
> actual input-reading going on underneath the @$self notation?
> If it's just dumping data from process memory, I should think
> one flush would be
Kevin Grittner writes:
> I find the TestLib.pm framework to be more friendly with the
> attached tweak to SimpleTee.pm. It's not a big deal, so if anyone
> objects I'll let it drop, and I don't think it merits anything
> fancier.
Just out of curiosity --- what's the rationale for flushing after
I find the TestLib.pm framework to be more friendly with the
attached tweak to SimpleTee.pm. It's not a big deal, so if anyone
objects I'll let it drop, and I don't think it merits anything
fancier.
Objections?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
