[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: flushing STDERR and STDOUT more often
|
From: |
Ole Tange |
|
Subject: |
Re: RFC: flushing STDERR and STDOUT more often |
|
Date: |
Thu, 18 Nov 2010 22:25:59 +0100 |
On Thu, Nov 18, 2010 at 6:42 PM, Markus F.X.J. Oberhumer
<markus@oberhumer.com> wrote:
> On 2010-11-18 13:50, Ole Tange wrote:
>> I think it is a bug that the flushes are not there already. This
>> example shows stderr for A coming after stdout for C, which never was
>> the intention of GNU Parallel:
>>
>> parallel -k 'echo stdout{}line;echo -n stderr{}noline 1>&2; echo
>> stdout{}' ::: A B C
>>
>> I do not think that one extra flush just before we close will ever be
>> a performance issue. And I would rather have GNU Parallel do the right
>> thing slowly than do the wrong thing fast (that is what xargs is for).
>
> Indeed. Which also makes me wonder if error handling is currently strict
> enough - I think that ALL errors from read/write/flush/close/... (and possibly
> also from print) should get detected and reported.
Show me an example (preferably similar to the above) where you get a
problem with current version and I will see what I can do.
/Ole