Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Jun 2015 11:00:20 -0700
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Julian Elischer <julian@freebsd.org>
Cc:        David Chisnall <theraven@FreeBSD.org>, Ian Lepore <ian@freebsd.org>, Alexander Kabaev <kabaev@gmail.com>, Marcel Moolenaar <marcel@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r284198 - head/bin/ls
Message-ID:  <20150613180020.GA1303@troutmask.apl.washington.edu>
In-Reply-To: <557C661F.8080104@freebsd.org>
References:  <201506100127.t5A1RdX6051959@svn.freebsd.org> <20150612204309.11dd3391@kan> <20150613024916.GA98218@troutmask.apl.washington.edu> <1434208622.1415.57.camel@freebsd.org> <C88CB169-12FE-4692-92AA-5C7D41BB61DF@FreeBSD.org> <557C661F.8080104@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 14, 2015 at 01:19:27AM +0800, Julian Elischer wrote:
> On 6/13/15 11:38 PM, David Chisnall wrote:
> > On 13 Jun 2015, at 11:17, Ian Lepore <ian@freebsd.org> wrote:
> >> If you would have told me a year ago that you had a simple scheme that
> >> could make 30 years of experience maintaining code for unix-like systems
> >> completely worthless I would have been skeptical, but it seems we're
> >> well on our way.
> > There is a lot of heckling and unhelpful hyperbole in this thread.  Reading the xo_emit format strings takes a little bit of getting used to, but the same is true of printf - it???s just that we???re already used to printf.  The structured parts (xo_open_container, xo_close_container and friends) are clear and descriptive.  The changes are fairly invasive, but the benefits are also very large for anyone who is wanting to automate administration of FreeBSD systems.
> >
> > If you have suggestions for how the libxo APIs could be improved, then please let us know - Phil is very reception to suggestions but objections along the lines of ???it???s not what I???m used to and changes sometimes break things so we should never have changes??? are not helpful.
> >
> > David
> >
> I made a suggestion for an alternate path in the previous thread.
> 
> https://lists.freebsd.org/pipermail/freebsd-current/2015-March/054855.html
> 
> but I have a job and kids so I can't object if I'm not listened to..
>   (no time to actually follow my own advice and produce working code.)
> 

I also pointed out the bloat

https://lists.freebsd.org/pipermail/freebsd-current/2015-March/054917.html

and the poor documentation

https://lists.freebsd.org/pipermail/freebsd-current/2015-March/054899.html

-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150613180020.GA1303>