X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=4E+JNsfA5opRSosuerSrtJ+UB9AQ5R/+PM0XgS2pdtw=;
	b=ewU8qX17bOrIGmn0J2E5cqb7xKvMFgyiY7PKv+rVRv8P8Kn9GCz8kAeiCIXFM7mlK2
	/S6ESxj6SxGcpAzDiV757V7SPgsT+yPinWPSxQ9daiI7R52uV4e+hj58M+Xe6YOtpD4d
	yl5re8PzsML3mhEd8LcELAJQ9xuTOLKSLPfxNiIwOAnCG4lO9DtQq5boHx3n5PeEwGQY
	L0NbawFmXUtaWv6B6DOcVcpToK0uHQEQSu6kK9aZ2MnnmB9J1BVcb7hPnd4DnWqiuH9u
	93pJT4qdL9BcUIwh/29RkESZZRrN5nsvRnrb4/mN+8w/st/ZzJmp2ZbxjV7Q6Am6gaba
	AFvQ==
MIME-Version:	1.0
X-Received:	by 10.194.109.97 with SMTP id hr1mr20187503wjb.38.1442169084264;
	Sun, 13 Sep 2015 11:31:24 -0700 (PDT)
In-Reply-To:	<201509131820.t8DIKUV5028308@envy.delorie.com>
References:	<CAC4O8c_XFEAgyrokrwwavB0C+OjWXCB5xptkVwMx2i_t960qFg AT mail DOT gmail DOT com>
	<201509120239 DOT t8C2dAiO026962 AT envy DOT delorie DOT com>
	<CAC4O8c_hq9WSaRtv1dUZLyFW-UaPBs-95JGB94EevdiLp8gQtg AT mail DOT gmail DOT com>
	<201509122223 DOT t8CMNhaZ024482 AT envy DOT delorie DOT com>
	<20150913004237 DOT 6f386c69 AT jive DOT levalinux DOT org>
	<CAC4O8c9ry51bjhjsozikYeWxTX9gGhDo-AnjSC99W8AQj5M0Vw AT mail DOT gmail DOT com>
	<201509131820 DOT t8DIKUV5028308 AT envy DOT delorie DOT com>
Date:	Sun, 13 Sep 2015 10:31:24 -0800
Message-ID:	<CAC4O8c9aM6t-U1THQX8aBwdkgP_p2yEC3NKJsjtnTf_E9qRYug@mail.gmail.com>
Subject:	Re: [geda-user] shortest way towards parsing .pcb files outside pcb
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, Sep 13, 2015 at 10:20 AM, DJ Delorie <dj AT delorie DOT com> wrote:
>> To the people who want a binary database format: I can see the
>> attractions.  Having the fastest possible parser could be a
>
> I did a project long ago that used a text file like the pcb-menu.res
> file (yaml-like).  It was stored on ascii but at one point we designed
> a binary representation designed for fast loading and smaller disk
> storage.  The speedup was much greater than we expected (it was a
> large commonly-used file).  We had utilities to convert between ascii
> and binary representations.
>
> So let's not rule out a binary *alternative* format too soon ;-)


Reasonable.  I'd make human-readable the default, to keep simple
things as simple as possible.  But I guess in principle there's no
reason not to have both.

- Raw text -