svn commit: r284198 - head/bin/ls

[Andrey Chernov]

On 13.06.2015 17:26, Julian Elischer wrote:
> On 6/13/15 10:49 AM, Steve Kargl wrote:
>> On Fri, Jun 12, 2015 at 08:43:09PM -0400, Alexander Kabaev wrote:
>>> On Wed, 10 Jun 2015 01:27:39 +0000 (UTC)
>>> Marcel Moolenaar <marcel at FreeBSD.org> wrote:
>>>
>>>> Author: marcel
>>>> Date: Wed Jun 10 01:27:38 2015
>>>> New Revision: 284198
>>>> URL: https://svnweb.freebsd.org/changeset/base/284198
>>>>
>>>> Log:
>>>>    Convert ls(1) to use libxo(3).
>>>>       Obtained from:    Phil Shafer <phil at juniper.net>
>>>>    Sponsored by:    Juniper Networks, Inc.
>>>>
>>> <SKIP>
>>>
>>> This broke all code that pipes output of the ls command to pipeline,
>>> such as 'ls | wc -l'. ls never exits and never output anything. Is
>>> there any purpose to libxo other than breaking stuff, which it achieves
>>> so splendidly?
>>>
>> -1 for libxo, which also makes code almost unreadable.
> +1 of the -1
> 
> my personal vote is to revert all libxo changes and banish it from
> /usr/src.

I already express my opinion in another thread, so just repeat it here.
When libxo starts to break things at very early stage, I perceive the
rest of the way to hell.

"Proper way to do this thing is to back out all changes and write
completely separate templates-based parser - xml/json/etc. writer." If
somebody love libxo code, use it in that parser/writer.

-- 
http://ache.vniz.net/

-- 
http://vniz.net/