Date: Thu, 10 Jul 2014 13:26:18 -0700 From: Jordan Hubbard <jordanhubbard@me.com> To: David Chisnall <David.Chisnall@cl.cam.ac.uk> Cc: Ed Schouten <ed@80386.nl>, Adrian Chadd <adrian@freebsd.org>, "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, Baptiste Daroussin <bapt@freebsd.org>, Nathan Whitehorn <nwhitehorn@freebsd.org>, Pietro Cerutti <gahr@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org> Subject: Re: svn commit: r268491 - head/usr.bin/users Message-ID: <172E965B-FCFE-4DA8-A845-08AEF931BD3B@me.com> In-Reply-To: <4B20737F-FB09-47DF-982F-E17F8989B83F@cl.cam.ac.uk> References: <201407101215.s6ACF3v1055260@svn.freebsd.org> <CAJOYFBCQjjN7ep12zivnmFjfeeP1SeoYa963mQbMJr9DD%2BfUnw@mail.gmail.com> <20140710152353.GF1812@ptrcrt.ch> <CAJOYFBDZiEpQ5e86%2BdBhRZobSjdf785bKBwh%2B3Eywhzn_iJJCQ@mail.gmail.com> <20140710154213.GG1812@ptrcrt.ch> <20140710155342.GB93051@ivaldir.etoilebsd.net> <CAJOYFBCMtnrdM96H9F86UsU=-7w-97N%2BKdBqYGihugD3W0%2BrbA@mail.gmail.com> <53BEC65D.10501@freebsd.org> <CAJ-VmomZ3o9YxCr6GSn0DEahOv0XXBow8Rgt10EoT6KAM2hjew@mail.gmail.com> <4B20737F-FB09-47DF-982F-E17F8989B83F@cl.cam.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 10, 2014, at 10:20 AM, David Chisnall <David.Chisnall@cl.cam.ac.uk> wrote: > This is important in a wider context. For example, in the project to add machine-readable output to core utilities, we'd like to be able to parse these into the same machine-readable format. Apple has the CoreFoundation library for this, which provides a load of stuff, but most importantly number, string, date, dictionary, and array types (i.e. the sorts of things that you'd want in JSON-like serialisation formats). Just as important as CoreFoundation are APIs like CFPreferences. I find it frankly horrifying that in the year 2014, anyone who writes a new daemon or system service will have to invent their own ad-hoc configuration file format in /etc (because, you know, there really aren't enough of them there now) as well as their own out-of-band mechanism for detecting when the configuration data changes. Having a data serialization format would the first step. - Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?172E965B-FCFE-4DA8-A845-08AEF931BD3B>