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 To: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] A fileformat library In-Reply-To: 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> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-1288035427-1451779449=:2176" 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 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--