From owner-freebsd-current@FreeBSD.ORG  Mon Mar  2 12:36:05 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 82AD0972
 for <freebsd-current@freebsd.org>; Mon,  2 Mar 2015 12:36:05 +0000 (UTC)
Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "cloud.theravensnest.org",
 Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4A451EF1
 for <freebsd-current@freebsd.org>; Mon,  2 Mar 2015 12:36:04 +0000 (UTC)
Received: from dhcp-172-17-158-227.eduroam.wireless.private.cam.ac.uk
 (global-1-26.nat.csx.cam.ac.uk [131.111.184.26])
 (authenticated bits=0)
 by theravensnest.org (8.15.1/8.14.9) with ESMTPSA id t22CZsxt025338
 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Mon, 2 Mar 2015 12:35:56 GMT (envelope-from theraven@FreeBSD.org)
X-Authentication-Warning: theravensnest.org: Host
 global-1-26.nat.csx.cam.ac.uk [131.111.184.26] claimed to be
 dhcp-172-17-158-227.eduroam.wireless.private.cam.ac.uk
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: Massive libxo-zation that breaks everything
From: David Chisnall <theraven@FreeBSD.org>
In-Reply-To: <54F42C6A.1000309@astrodoggroup.com>
Date: Mon, 2 Mar 2015 12:35:48 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8C7FA31-FE54-4514-9971-92B68C61DDF6@FreeBSD.org>
References: <54F31510.7050607@hot.ee> <54F34B6E.2040809@astrodoggroup.com>
 <CAG=rPVfcB1Fy_8mHq-t5Ay07yrzuSGthQ0ZcGzvp0XG9gSSzkg@mail.gmail.com>
 <54F35F29.4000603@astrodoggroup.com>
 <F1683E9A-6004-4749-BD6E-A5B2472F6C77@FreeBSD.org>
 <75C49F53-C675-4712-A446-370025EED037@me.com>
 <AEB1CF1E-9429-4C86-A59E-E1C86C019098@FreeBSD.org>
 <54F42C6A.1000309@astrodoggroup.com>
To: Harrison Grundy <harrison.grundy@astrodoggroup.com>
X-Mailer: Apple Mail (2.2070.6)
Cc: freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2015 12:36:05 -0000

On 2 Mar 2015, at 09:24, Harrison Grundy =
<harrison.grundy@astrodoggroup.com> wrote:
>=20
> It would seem like the libxo stuff runs the risk of becoming this same
> API.

Why?  The 'API' in the case of an libxo-ised program is a stream on =
stdout that is then consumed by a JSON or XML parser. XML and JSON are =
intrinsically extensible formats.  This is *the entire point* of libxo: =
that we can extend the output from these tools without breaking things =
that wish to consume them and which currently rely on fragile parsers.

David