X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Sun, 3 Jan 2016 01:04:09 +0100 (CET)
From:	Roland Lutz <rlutz AT hedmen DOT org>
To:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject:	Re: [geda-user] A fileformat library
In-Reply-To:	<CAC4O8c-zt8B=joDd+ws77D2jt6aZf3MWfR_dAvpzGcNuBrTURQ@mail.gmail.com>
Message-ID:	<alpine.DEB.2.11.1601030040320.2176@newt>
References:	<1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <CAJXU7q_mXmipJ1fLvLpuLvnYjktV2SHoA+bG=L5+E-EfdygeOA AT mail DOT gmail DOT com> <s6n37uumanm DOT fsf AT blaulicht DOT dmz DOT brux> <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>
User-Agent:	Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version:	1.0
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

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1288035427-1451779449=:2176
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

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.
>
> Getting the data model right is also the hard bit - unfortunately.

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.

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?

The part of parsing a .sym/.sch file which can potentially become easier 
with YAML is as simple as a sscanf(3).  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.

--8323329-1288035427-1451779449=:2176--

- Raw text -