X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Wed, 23 Dec 2015 06:50:10 +0100 (CET) X-X-Sender: igor2 AT igor2priv To: geda-user AT delorie DOT com X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu 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> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 On Tue, 22 Dec 2015, John Doty wrote: > > On Dec 22, 2015, at 10:16 PM, gedau AT igor2 DOT repo DOT hu wrote: > >> 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.