From owner-freebsd-current@freebsd.org Sun Nov 15 18:30:16 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92DEEA2FF80 for ; Sun, 15 Nov 2015 18:30:16 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 592D41A6B; Sun, 15 Nov 2015 18:30:16 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by igbxm8 with SMTP id xm8so43734226igb.1; Sun, 15 Nov 2015 10:30:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kd52P4okpFDYiRAA4bjt2Rcy0Rxfx+bMvitrPFWk2Y4=; b=QKqPfDTqWCSG4h0apRcCPU9grGRo0Oud11fXtQVq+rWqJEnQIDN6vbSXS6UI0Rs+G8 MtFYtDPtyZUqQkSF1hQzTKdFqFP8LcO3rtzoVmCPumbSz1BkwWleke4HN+tTA2l2IPvs 5ue0ETKtLRj+fLKU/FZsLYxNJIjyqsPvAvcBOJO7CAnfmWNnEh3wWNjFsk+9Ck5vzAP0 xrVtQWRwvZMMOLC4NyCh1zafTOe29T+DqF+vlV4rFLWeifBEWWkGlmy67ldmd4QBIZ5z 4zPMrzpaxnZW6xDIXkCCLZ3h9XHH6om0m3J9qyuJwUuZc/tPMHODBrhJ3xOGqlHxg1tK PZjQ== X-Received: by 10.50.55.72 with SMTP id q8mr13305001igp.2.1447612215795; Sun, 15 Nov 2015 10:30:15 -0800 (PST) Received: from [192.168.20.7] (c-24-16-212-205.hsd1.wa.comcast.net. [24.16.212.205]) by smtp.gmail.com with ESMTPSA id lo2sm5017998igb.17.2015.11.15.10.30.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 15 Nov 2015 10:30:14 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? From: NGie Cooper In-Reply-To: <5648CD87.4020305@freebsd.org> Date: Sun, 15 Nov 2015 10:30:12 -0800 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <35BF04D9-332D-49E5-8927-AB542CADDB98@gmail.com> References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> <702A1341-FB0C-41FA-AB95-F84858A7B3A4@rdsor.ro> <5648C60B.6060205@freebsd.org> <6EDFB74B-2206-46E7-85F7-8DE05FB6D325@gmail.com> <5648CA60.3060800@freebsd.org> <5648CC0F.6050708@freebsd.org> <5648CD87.4020305@freebsd.org> To: Allan Jude X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Sun, 15 Nov 2015 18:30:16 -0000 > On Nov 15, 2015, at 10:23, Allan Jude wrote: =85 > Also, libxo now supports the versioning of output, to make it possible > for your json parser to detect when a change to the schema has been = made. This is the ideal scenario, yes, if there was some design around the = libxo=92ification (even man page documentation would have been nice, but = that wasn=92t done :/). However, as I=92ve said many times before: no = spec, no tests -> not useful to endorse to others because things can = change at any given point in time and I don=92t want to be the support = hub for all things libxo at $work. Thanks, -NGie=