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=_031E16E9-91AB-471D-896F-CEC3B80B7ADB"; 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: Sat, 2 Jan 2016 17:26:29 -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> 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=_031E16E9-91AB-471D-896F-CEC3B80B7ADB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Jan 2, 2016, at 5:04 PM, Roland Lutz wrote: > On Thu, 24 Dec 2015, Peter Clifton (petercjclifton AT googlemail DOT com) = [via > geda-user AT delorie DOT com] wrote: >> Getting the data model right is almost completely independent of the = rest - even if some may work more elegantly than others. >>=20 >> Getting the data model right is also the hard bit - unfortunately. >=20 > I absolutely agree. I've been working hard to get the in-memory data = representation for Xorn right, and the main thing which keeps me from = defining PCB object types right now is that I haven't found a convincing = data model for these yet. >=20 > On Sun, 27 Dec 2015, Britton Kerin (britton DOT kerin AT gmail DOT com) [via = geda-user AT delorie DOT com] wrote: >> Simple though it is, the effort of parsing it is not zero and is = mostly a waste. Modern language have built-in serialization, and with = YAML you get a cross-language version of that plus a well-defined = human-readable file format. What's not to like? >=20 > The part of parsing a .sym/.sch file which can potentially become = easier with YAML is as simple as a sscanf(3). Except that what we have is already easy to parse with sscanf() and = other things. We have a lot of infrastructure based on what we have: = symbol generators, refdes renumberers, ... > After extracting the value strings from the file, you still have = parse and validate them no matter whether they have been stored in a = .sym/.sch or YAML file. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_031E16E9-91AB-471D-896F-CEC3B80B7ADB 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 iQIcBAEBCgAGBQJWiGq1AAoJEF1Aj/0UKykRhJYP/Amq7cVOPYKJKgvkcB0AbZeK lCv1YvMXFctAqilvTJzAI5bZ+L9Ge3N8WziWAYdKOYjANCkZC0/5HUByF6Uv99do Brym2Lp9JjejCJ+9TLCEOc8+odwrZcOvlKdZuocPBWRZ0+fOznwa/m0YgX/OsW4f 2FrtN3VBAxaQ3KlqOJwFVMyXMWawRmr3UkZkRMa1Y91uaTXmrYY6KTNL/y5ANA7+ IqBu+CUXKp8Ub+BmkuuG0ImNGzKrjETdgbvS827JlFOdyE7zr1geIUzf5TR6v+eV jZzl3yQe2LbR2hGEFoPbrI4fdr8Chklq3/i1D9SAOx/dMMbgu3oEzrHjKiQVYh4h 5YdvQaiiHdjtbiHWfWdyvGASZciHk4r9OmzenYUatir7THS/a7RA1ZQFOozQFs9u eQi41MkoguFtcadcOMrGKNku/rEWyeYi8u6QcmByIKL9MCLoJNvArkDIw4+rxrHj Hu8qcC2vAfIr+eVQ6MwsqfUJHomeI1OZelplppwvwb3Y0a3PjqmFmaqoxPz5WjOV ojim1+RvvtoQHc+YdfWEYfJyBLFYTMbLsumSlBV6temJOWev9lD0kWD0kvSOBP2n zDLazc6x+1mv5K0QeXGsdDSdm+k0b5MlL+BLIdGzg5fkU51k58v0DLQrFIwd4L+x BasZLQ/Hv2SK5d05igga =Y8C3 -----END PGP SIGNATURE----- --Apple-Mail=_031E16E9-91AB-471D-896F-CEC3B80B7ADB--