From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: lazyvirus@gmx.com
Received: from krantz.zx2c4.com (localhost [127.0.0.1])
 by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 8feedd8a
 for <wireguard@lists.zx2c4.com>;
 Wed, 17 May 2017 14:03:29 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21])
 by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 7581aab1
 for <wireguard@lists.zx2c4.com>;
 Wed, 17 May 2017 14:03:29 +0000 (UTC)
Date: Wed, 17 May 2017 16:14:48 +0200
From: Bzzzz <lazyvirus@gmx.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: Text-based IPC for Userspace Implementations
Message-ID: <20170517161448.6b56f107@msi.defcon1>
In-Reply-To: <CAHmME9p4wtwUG8_4KvjdLcNcE33=BTWTNmWWX_eMWkiE=Z3Grw@mail.gmail.com>
References: <CAHmME9pGX9zH+A9ouz0g8g6R7ZheZ=sKu_seAZ8r-DtBRdY_Rw@mail.gmail.com>
 <87vap1gd2w.fsf@alrua-kau>
 <358B5193-8D9F-472F-8202-B81BAA022FDD@titanous.com>
 <1500fe21-c423-b34d-adf5-463b5d483cbf@higgsboson.tk>
 <CAHmME9p4wtwUG8_4KvjdLcNcE33=BTWTNmWWX_eMWkiE=Z3Grw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
List-Id: Development discussion of WireGuard <wireguard.lists.zx2c4.com>
List-Unsubscribe: <https://lists.zx2c4.com/mailman/options/wireguard>,
 <mailto:wireguard-request@lists.zx2c4.com?subject=unsubscribe>
List-Archive: <http://lists.zx2c4.com/pipermail/wireguard/>
List-Post: <mailto:wireguard@lists.zx2c4.com>
List-Help: <mailto:wireguard-request@lists.zx2c4.com?subject=help>
List-Subscribe: <https://lists.zx2c4.com/mailman/listinfo/wireguard>,
 <mailto:wireguard-request@lists.zx2c4.com?subject=subscribe>

On Wed, 17 May 2017 16:01:16 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:

> 
> Right. I'd indeed be very amused to see a JSON parser land in the
> Linux kernel.

Perhaps, this could do the trick: https://github.com/martinh/libconfuse

Jean-Yves