From owner-freebsd-current@FreeBSD.ORG Mon Mar 2 09:14:32 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A08E24BF for ; Mon, 2 Mar 2015 09:14:32 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 709DF3E3 for ; Mon, 2 Mar 2015 09:14:32 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id t229ETkJ003286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 2 Mar 2015 01:14:30 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54F429EF.5050400@freebsd.org> Date: Mon, 02 Mar 2015 01:14:23 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Harrison Grundy , freebsd-current@freebsd.org Subject: Re: Massive libxo-zation that breaks everything References: <54F31510.7050607@hot.ee> <54F34B6E.2040809@astrodoggroup.com> <54F35F29.4000603@astrodoggroup.com> In-Reply-To: <54F35F29.4000603@astrodoggroup.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2015 09:14:32 -0000 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 > > >