X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 X-Authenticated-UID: jpd AT noqsi DOT com Content-Type: multipart/signed; boundary="Apple-Mail=_47875EB9-9D5A-48EB-B290-768A1E2FABE2"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] A fileformat library X-Pgp-Agent: GPGMail 2.5.2 From: John Doty In-Reply-To: Date: Sun, 3 Jan 2016 20:25:32 -0700 Message-Id: References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG>

<20151222232230 DOT 12633 DOT qmail AT stuge DOT se> <0F6F1D0F-4F07-48EA-90FE-836EAD4E2354 AT noqsi DOT com> <0FCF3774-F93C-4BFF-BB61-636F75DCCACB AT noqsi DOT com>

<20160103173859.ce123a8957899e5c3e! 496d9b AT gmail DOT com> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) 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 --Apple-Mail=_47875EB9-9D5A-48EB-B290-768A1E2FABE2 Content-Type: multipart/alternative; boundary="Apple-Mail=_202CD72B-CA51-4E3A-BAD9-A8D49192D6CE" --Apple-Mail=_202CD72B-CA51-4E3A-BAD9-A8D49192D6CE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Jan 3, 2016, at 7:11 PM, Britton Kerin (britton DOT kerin AT gmail DOT com) [via = geda-user AT delorie DOT com] wrote: >=20 > 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] = 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=3DRESISTOR > > 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. >=20 > 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. >=20 > 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. >=20 > 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. >=20 > 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. A stronger argument for text is that you can process it with = text-oriented tools. >=20 > Britton John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_202CD72B-CA51-4E3A-BAD9-A8D49192D6CE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

On Jan 3, 2016, at 7:11 PM, Britton = Kerin (britton DOT kerin AT gmail DOT com) = [via geda-user AT delorie DOT com] = <geda-user AT delorie DOT com>= wrote:

On Sun, Jan 3, 2016 at 7:38 AM, Nicklas Karlsson = (nicklas DOT karlsson17 AT gmail DOT com<= /a>) [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=3DRESISTOR
> 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.

A stronger = argument for text is that you can process it with text-oriented = tools.

Britton

John Doty Noqsi = Aerospace, Ltd.

http://www.noqsi.com/

jpd AT noqsi DOT com

= --Apple-Mail=_202CD72B-CA51-4E3A-BAD9-A8D49192D6CE-- --Apple-Mail=_47875EB9-9D5A-48EB-B290-768A1E2FABE2 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWieYtAAoJEF1Aj/0UKykRo6QQAK8LIB7qtzwR4/XN9NQmzxor TSJqsgwbvb8XsxYFB0uM3GR5reRC8QqkLHM5mlBVKpeo421VRALkXNeSAiATfy5k fPKyUiSy4gzGahnuNlvMuWCoFGFpABewwXcESraVqh/MxD93ulp7OrXXTebBvf61 x3kIx+dXtHgUkeFsxXxzIzh1mNCpmqMdM+KXLgPS0KljrphnNIf4T0k8we5cgYzt zKfS2cNvfUVVUyuQKT4FSHzSZhnZotM+hpHB8EQGsq8u1XcrJ5jmDY5j67duUzAO PkiAqbtnNRJ9mnpHFydQaJajczupYwKRyky2J0W373lmTsdk3CFwVyTNCG6JxIn8 E3nu5uX2/yqCVS/UdFovzetOJt1U1MevXqB/p8gOageitucFtuoPrNCWWTFQxf89 IjJDpCUnn8CNPK8bOMs4o5+CJMyPwToIAJSnQrnLVvXVjtAuwIynC3kP/+320irx AhhZiB0hlm1iGyAoJUhkJy/KaCvZBcGL+SyyNJqTtCgbvxgr7+rl3HJVEvQ2QYpl /FVfO+LoweoER5G3lwePFNP3dQ2AhMCJugqqno3XRjn2AIlHm4BX3jUVnmTFSPBY 47qXN75SStP1lJ3Lbko0KSIXCSPKUkIGSBdPYgFGixownhOS6zrW2ml5kJiwQCil 91b/WgLrP+9jct+ongh3 =1qR6 -----END PGP SIGNATURE----- --Apple-Mail=_47875EB9-9D5A-48EB-B290-768A1E2FABE2--