From owner-freebsd-current@FreeBSD.ORG Mon Mar 2 09:26:02 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 7C662BC8; Mon, 2 Mar 2015 09:26:02 +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 41553750; Mon, 2 Mar 2015 09:26:01 +0000 (UTC) Received: from [192.168.0.7] (cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61]) (authenticated bits=0) by theravensnest.org (8.15.1/8.14.9) with ESMTPSA id t229Pwl1024388 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Mar 2015 09:26:00 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61] claimed to be [192.168.0.7] 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 In-Reply-To: <54F42A82.1020308@freebsd.org> Date: Mon, 2 Mar 2015 09:25:53 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <54F31510.7050607@hot.ee> <54F34B6E.2040809@astrodoggroup.com> <54F35F29.4000603@astrodoggroup.com> <54F36431.30506@freebsd.org> <54F42A82.1020308@freebsd.org> To: Julian Elischer X-Mailer: Apple Mail (2.2070.6) Cc: freebsd-current@freebsd.org, Allan Jude 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:26:02 -0000 On 2 Mar 2015, at 09:16, Julian Elischer wrote: >=20 > if we develop a suitable post processor with pluggable grammars, we = save a lot of work. > given enough examples you could almost have automatically generated = grammars. This decoupled approach is problematic. A large part of the point of = libxo is to allow changing the human-readable output without breaking = tools that consume the output. Now I need to keep the tool that = consumes it and the tool that produces it in sync, so that's an extra = set of moving parts. When you throw jails with multiple versions of = world into the mix, it becomes a recipe for disaster. David