Date: Mon, 2 Mar 2015 12:35:48 +0000 From: David Chisnall <theraven@FreeBSD.org> To: Harrison Grundy <harrison.grundy@astrodoggroup.com> Cc: freebsd-current@freebsd.org Subject: Re: Massive libxo-zation that breaks everything Message-ID: <F8C7FA31-FE54-4514-9971-92B68C61DDF6@FreeBSD.org> In-Reply-To: <54F42C6A.1000309@astrodoggroup.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2 Mar 2015, at 09:24, Harrison Grundy <harrison.grundy@astrodoggroup.com> wrote: > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F8C7FA31-FE54-4514-9971-92B68C61DDF6>