On 20 Nov 2013, at 21:40, Theo de Raadt <dera...@cvs.openbsd.org> wrote:

>>>>> FreeBSD and Dragonfly BSD have this option in tr. So, this actually
>>>>> improves portability.
>>> It's just spreading the disease. portable means it works everywhere.
>>> Increasing the number of people who can write nonportable code is not
>>> the same as increasing portability.
>> How many others have to adopt it before it's considered portable, then?
> It is portable when all of them have it.  Since you can't fix the past,
> we must be very conservative in our approach.

In this case `portable' simply means `unavailable'.  And that's good.  :)
DragonFly has it solely because of the shared FreeBSD history, not because
it's being used a lot.

>> It's possible, as mentioned elsewhere, that simply making tr be
>> unbuffered by default is the better move, and ignore -u for
>> compatibility with FreeBSD and Dragonfly BSD.

How will that make things better?

Reply via email to