Date: Mon, 02 Mar 2015 01:14:23 -0800 From: Julian Elischer <julian@freebsd.org> To: Harrison Grundy <harrison.grundy@astrodoggroup.com>, freebsd-current@freebsd.org Subject: Re: Massive libxo-zation that breaks everything Message-ID: <54F429EF.5050400@freebsd.org> In-Reply-To: <54F35F29.4000603@astrodoggroup.com> References: <54F31510.7050607@hot.ee> <54F34B6E.2040809@astrodoggroup.com> <CAG=rPVfcB1Fy_8mHq-t5Ay07yrzuSGthQ0ZcGzvp0XG9gSSzkg@mail.gmail.com> <54F35F29.4000603@astrodoggroup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/1/15 10:49 AM, Harrison Grundy wrote: > Thanks! > > That does seem useful, but I'm not sure I see the reasoning behind > putting into base, over a port or package, since processing XML in base > is a pain, and it can't serve up JSON or HTML without additional > utilities anyway. > > (If I'm reviving a long-settled thing, let me know and I'll drop it. I'm > trying to understand the use case for this.) To me it would almost seem more useful to have a programmable filter for which you could produce parse grammars to parse the output of various programs.. thus ifconfig -a | xmlize -g ifconfig | your-favourite-xml-parser with a set of grammars in /usr/share/xmlize/ then we could use it for out-of-tree programs as well if we wrote grammars for them.. The sentiment of machine-readable output is nice, but I think it's slightly off target. we shouldn't have to change all out utilities, and it isn't going to help at all with 3rd party apps, e.g. samba stuff. A generally easy to program output grammar parser would be truely useful. and not just for FreeBSD. I've been watching with an uncomfortable feeling, but it's taken me a while to put my finger on what it was.. > > --- Harrison > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54F429EF.5050400>