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=Yf6Den9gCz1kJXmM3pL8DwpECpz/ISKvRqoi2e3I7/I=;
        b=V0DVtJFP4WMm/u0E4Bv4qFIOpJYWp9ShtfYDcOz5dTkxUP4ryHp1jqEeINsE5Fu9qX
         yKONgIL/6VBIcJ8fSgsZ+W441Pt6/beZLdyqB9Lgvqvd5nIowVZYr5YpKEaNv8frr42B
         3Qgdhagd4agRC/Mf1KMtnlf7ArlGos8AkvCEbcHXsV3iCt+AGyIbFKwYLK6MQHcOLH9y
         UQYVKvwg0Qf+TT5tYH2vRHzFQpamNvDWp9aF0b53NSxJLVCOdyJuVTlczsdcpQQroL7E
         tj1Ur4g9KkArHBhG+0dMebNI4NldkNekm24fM/IYp+89C8qsD8nQE8zRN8X7HhqJXxLn
         QnFw==
MIME-Version: 1.0
X-Received: by 10.194.6.98 with SMTP id z2mr91902051wjz.101.1451873468837;
 Sun, 03 Jan 2016 18:11:08 -0800 (PST)
In-Reply-To: <20160103173859.ce123a8957899e5c3e496d9b@gmail.com>
References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG>
	<CAJXU7q_qxdvJaejF-VcY=u7VHZ-zrfrc+Z7-qSwfFyPdy-umxw AT mail DOT gmail DOT com>
	<B02363CD-469D-493A-AC15-1D5DC7836982 AT noqsi DOT com>
	<20151222232230 DOT 12633 DOT qmail AT stuge DOT se>
	<0F6F1D0F-4F07-48EA-90FE-836EAD4E2354 AT noqsi DOT com>
	<CAM2RGhTficnys3a4xs=UBFvk8aPwpzYWUADFLP_pUQ+R1iKs0g AT mail DOT gmail DOT com>
	<0FCF3774-F93C-4BFF-BB61-636F75DCCACB AT noqsi DOT com>
	<CAC4O8c_UAiFE-vGfoE2tXppHLhaa0dSYz9o_rkdCBo7_SRRtxw AT mail DOT gmail DOT com>
	<FFBE7623-E240-4798-96B0-2BECF56C8E29 AT noqsi DOT com>
	<CAC4O8c980g1gj15=5njstC_BT-WYDgKQx9BRycdFKA8OvgtiOg AT mail DOT gmail DOT com>
	<B54C0E1F-1986-4C79-9F70-7F1919B8B26D AT noqsi DOT com>
	<CAC4O8c9bxJP1eMG4yz3YwKkQJRmsDGmLQ0aMd5pJRyu0WpdCtQ AT mail DOT gmail DOT com>
	<C1CFCCEE-C64A-4E49-AA64-446C061656D6 AT noqsi DOT com>
	<CAC4O8c-zt8B=joDd+ws77D2jt6aZf3MWfR_dAvpzGcNuBrTURQ AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1601030040320 DOT 2176 AT newt>
	<D9825C8C-B6FD-4C7F-A8D5-B8AF06253B72 AT noqsi DOT com>
	<CAC4O8c_R5xWLmzj_cz0g0mPWNs6mR4efjXKGBoup8YO6nwnPTA AT mail DOT gmail DOT com>
	<20160103173859 DOT ce123a8957899e5c3e496d9b AT gmail DOT com>
Date: Sun, 3 Jan 2016 17:11:08 -0900
Message-ID: <CAC4O8c_tZ52RNV5qD3YJmd-Hhoi6j62pSZZt54S2z_L9YU1RxQ@mail.gmail.com>
Subject: Re: [geda-user] A fileformat library
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
Content-Type: multipart/alternative; boundary=047d7b5d3e645e797e052878a2a1
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
Precedence: bulk

--047d7b5d3e645e797e052878a2a1
Content-Type: text/plain; charset=UTF-8

On Sun, Jan 3, 2016 at 7:38 AM, Nicklas Karlsson (
nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <
geda-user AT delorie DOT com> wrote:

> > As I've mentioned previously I'm talking pcb, which is a more painful
> > format to parse (such that so far as I'm aware the parser in pcb is the
> > only one).  Personally I find formats like this:
> >
> >   device=RESISTOR
> >   T 44400 49300 5 10 1 1 90 0 1
> >
> > substantially less readable than ones with field names, but they are
> indeed
> > easy to parse.  The pcb format is quite a bit more elaborate and the
> > savings from not rolling your own parser are more significant.
>
> Yes this is simple to parse, use little file space but do not have field
> name. To use little file space and be simple to parse is actually two good
> properties of a file format.
>
> Lack of field names may be worked around by having a list of field names
> in the beginning. If this list of field names is sorted according to how
> often they are used and each row only have to list used values it would
> probably be a file format with rather good properties.
>
> To enumerate the field names at the beginning of the file may also be a
> solution. Or maybe to use representation of data structures from a
> programming language.
>

Although these are good measures, once you adopt them you may start asking
yourself why you aren't just using a binary format.  The argument for text
is that you can glance at a chunk of it and easily tell what's going on.

Britton

--047d7b5d3e645e797e052878a2a1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Sun, Jan 3, 2016 at 7:38 AM, Nicklas Karlsson (<a href=3D"mailto:nicklas=
.karlsson17 AT gmail DOT com">nicklas DOT karlsson17 AT gmail DOT com</a>) [via <a href=3D"ma=
ilto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] <span dir=3D"ltr">&l=
t;<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delo=
rie.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">&gt; As I&#=
39;ve mentioned previously I&#39;m talking pcb, which is a more painful<br>
&gt; format to parse (such that so far as I&#39;m aware the parser in pcb i=
s the<br>
&gt; only one).=C2=A0 Personally I find formats like this:<br>
<span class=3D"">&gt;<br>
&gt;=C2=A0 =C2=A0device=3DRESISTOR<br>
&gt;=C2=A0 =C2=A0T 44400 49300 5 10 1 1 90 0 1<br>
&gt;<br>
</span><span class=3D"">&gt; substantially less readable than ones with fie=
ld names, but they are indeed<br>
</span>&gt; easy to parse.=C2=A0 The pcb format is quite a bit more elabora=
te and the<br>
<span class=3D"">&gt; savings from not rolling your own parser are more sig=
nificant.<br>
<br>
</span>Yes this is simple to parse, use little file space but do not have f=
ield name. To use little file space and be simple to parse is actually two =
good properties of a file format.<br>
<br>
Lack of field names may be worked around by having a list of field names in=
 the beginning. If this list of field names is sorted according to how ofte=
n they are used and each row only have to list used values it would probabl=
y be a file format with rather good properties.<br>
<br>
To enumerate the field names at the beginning of the file may also be a sol=
ution. Or maybe to use representation of data structures from a programming=
 language.<br></blockquote><div><br></div><div style=3D"">Although these ar=
e good measures, once you adopt them you may start asking yourself why you =
aren&#39;t just using a binary format.=C2=A0 The argument for text is that =
you can glance at a chunk of it and easily tell what&#39;s going on.</div><=
div>=C2=A0</div><div style=3D"">Britton</div></div></div></div>

--047d7b5d3e645e797e052878a2a1--