From owner-freebsd-current@freebsd.org Sun Nov 15 18:16:49 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 8A555A2FBD4 for ; Sun, 15 Nov 2015 18:16:49 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 65A75106E for ; Sun, 15 Nov 2015 18:16:48 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 7AAC0DC3A; Sun, 15 Nov 2015 18:16:48 +0000 (UTC) Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? To: Garrett Cooper 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> Cc: freebsd-current@freebsd.org From: Allan Jude Message-ID: <5648CC0F.6050708@freebsd.org> Date: Sun, 15 Nov 2015 13:16:47 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rs14iHBM4dtbESeBBridiTD08piUqJdfV" 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:16:49 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --rs14iHBM4dtbESeBBridiTD08piUqJdfV Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-11-15 13:14, Garrett Cooper wrote: >=20 >> On Nov 15, 2015, at 10:09, Allan Jude wrote: >=20 > ... >=20 >> The big difference is, a json parser isn't going to blow up if a new >> field gets added in the middle, and your awk/grep/sed script probably = will. >=20 > That's a plus to those formats, yes, but if someone changes the field n= ame (which can happen today, on a whim, and would go unnoticed for a whil= e because no tests/spec), you'll run into a KeyError in Python or an equi= valent error message in your language of choice. >=20 > Thanks, >=20 But, if the same change was made to a pure text output, then our 'column 3' would suddenly be username instead of ip address, and your program would not work at intended either. so at least json would give you a warning. So, the need for a spec on the output is not specific to encoded outputs, changing the output in text is just as disruptful. --=20 Allan Jude --rs14iHBM4dtbESeBBridiTD08piUqJdfV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWSMwPAAoJEBmVNT4SmAt+QikQAOzAIg4wCBJozkDlBq9xuQAn mgL0UVO5rJ3TBgbBfeFji0tn0FiHTQYhseu7u+TAKb2eWRb/XGz8VsV8b7BOQUGt TGx8hvlYTFRaVnZ9XYYMej6bYSbFxNla2CSL3vu9XImmv/B9qaqYhIFb6Q6nosqD p9z5RXzU0ehvX3T9ZXe8DRMMfy7zDf/0kenNVC8SHfZ2bdB9g83taikJodwoJHbF 81FKyRnURVK7MMK4oLSOHMaBTdr81v0Zh2ZTYQzglVQKZP+UGTOBk3cMZv95OgPt YL2Wde15bEVJIEHBKJZYbwDr21KqTPPELuFCObQ1M7F82xGlAZBtnx4ZUXap8QmD gn1WlrzP2DhhimdXQCpugIHtL/1bcwMVCXhQn/O2iaDmlCxyFvHdTTRawmb6N7/i MOL/TGg2wqIcOn837lugO75G3hzCNagwl+VSc1MIkKJN1VrCapjNRcm6lDjSCgbZ BfS6SQEBjzZirit/RAkz77MJmB21TGpf6PWaRpFQAZupEuHNmxjCFBqQn7OOoCe/ XesAuZ2qA+wbbyPQvgspJvHucFpjJvgBqeqSwX6vzN+UA+6aQoXq1YMRoSUZjaMc o17/Quik4JIsff8GIm3oN1XhRO4vIiqPbowc0qoh2FmvZN0Ky20392seFC3M5ZSB zxN4Zo/gVzaSlsGKSoLd =zd8n -----END PGP SIGNATURE----- --rs14iHBM4dtbESeBBridiTD08piUqJdfV--