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=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=3KwiEN4UCpyfa7J+EqJ3Y4hsv1nIyfjHn1p2JkmC8G4=; b=ONRNuq3wscWyTyCdi9enw84q5fsFlb2cocDD57nnQYqu7/jVQYfYgIxRnEXeQ8inwb 2AN42tzewhZPTOa4ymdC2Of2UROnhkYZV6rmna/hTdUe1sYMHHFUu7/cNAkhW7tiIrYW 82z/Kujr4nJH7Ho2nppVWNcRLgzomQ4hFe60Dd/znAxVGl5RIt+HRnoUp37CI5LwG4Wf cD4Ab54OqcAP9nftvKMcQ4Mz7wrKbUleE2i9vXCsnRt9eltajX1t8F4iDvnm6ZxdvbEl bWIqzP7dHojR0pTxg1gzsmzpKmjvmT3zpwCBRWp9dg6wLV6FBjTyDtVVot6hh0O5Vpz8 JZmw== X-Received: by 10.194.249.97 with SMTP id yt1mr36507768wjc.89.1450889132086; Wed, 23 Dec 2015 08:45:32 -0800 (PST) Date: Wed, 23 Dec 2015 17:45:24 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] A fileformat library Message-Id: <20151223174524.d0808db9298359f083db847f@gmail.com> In-Reply-To: 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> X-Mailer: Sylpheed 3.4.3 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 > >>> It's painful, and I am fully aware of risking a rewrite if the file format changes. I am also fully aware of the fact that libgeda exists and it is invented exactly for this kind of stuff. > >> > >> Going through libgeda doesn?t insulate you from change, since the libgeda API is no more stable than the file format. > > > > > > That's clear. By "is invented exactly for this kind of stuff" I didn't mean "invented to avoid (API) changes" but "invented to avoid the need to write parsers by hand" - in the sense that one can use it instead of writing a parser. > > But is it *really* so hard to write a parser for the .sch format? Seems pretty trivial to me. Easier than figuring out what an extra layer is actually doing and wrapping it in yet another layer to support what *I* need. That’s why I like simple, transparent file formats. > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com Extra layers certainly could be an extra burden. I develop software for micro controllers and once an extra software driver layer is added it is no longer enough to read data sheet and even worse usually usually use dynamic handling there much simpler static handling would be better. Nicklas Karlsson