Date: Sun, 15 Nov 2015 10:14:23 -0800 From: Garrett Cooper <yaneurabeya@gmail.com> To: Allan Jude <allanjude@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: libXO-ification - Why - and is it a symptom of deeper issues? Message-ID: <F9E0136C-9BFA-4FE7-A623-9F5D8871A6D1@gmail.com> In-Reply-To: <5648CA60.3060800@freebsd.org> References: <0650CA79-5711-44BF-AC3F-0C5C5B6E5BD9@rdsor.ro> <CAJ-Vmokfo_BGWji9TrgQ40oRxqht9-2iEZVon7aQxR_93Ufxyg@mail.gmail.com> <702A1341-FB0C-41FA-AB95-F84858A7B3A4@rdsor.ro> <CAJ-VmoniBAmWTf9MkCCMYhRbPLc=0%2Bz5kRSijXfqX9VZvm8jDg@mail.gmail.com> <5648C60B.6060205@freebsd.org> <6EDFB74B-2206-46E7-85F7-8DE05FB6D325@gmail.com> <5648CA60.3060800@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 15, 2015, at 10:09, Allan Jude <allanjude@freebsd.org> wrote: ... > 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= . That's a plus to those formats, yes, but if someone changes the field name (= which can happen today, on a whim, and would go unnoticed for a while becaus= e no tests/spec), you'll run into a KeyError in Python or an equivalent erro= r message in your language of choice. Thanks,=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F9E0136C-9BFA-4FE7-A623-9F5D8871A6D1>