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=vRdFKKO7lR2V/a6UP4jmyWbU3o2oWNA5+8mAMG+oB3s=; b=BJd+RD9ZQMau8rSP6RttZVToP/bs4uyWPjSOt1eRnylXREUM1TLO1QxYjFFALgzL+g ZjxfzkQ65NTAzspTD5l/C05Tl5UD0DwADOsZZt5w5PDSDRKKyvhdWPBpAV279Zpn2RPC mdjTCHBbqEejeUPKUEPZkr67Bc44/a6aDr2r2WxSLhWltrfWkpEfgrt2uboNZeoOfKfu yV7EdTw++v1b31drCM+PMM66k83avJtcovlxESOUNK6xOrkNYhGvnUgLkFHk/hln8wvc MFVGYdbzSaSTakFM7la/Hhx7y5C46K/hHI2cdc5kdANYnPA9rw9Nt2io4Jsl6+8hyP9j mhug== X-Received: by 10.180.76.231 with SMTP id n7mr13715675wiw.65.1442128822111; Sun, 13 Sep 2015 00:20:22 -0700 (PDT) Date: Sun, 13 Sep 2015 09:20:16 +0200 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] shortest way towards parsing .pcb files outside pcb Message-Id: <20150913092016.bc0a237e5f1d94f561578533@gmail.com> In-Reply-To: <201509122223.t8CMNhaZ024482@envy.delorie.com> References: <201509120239 DOT t8C2dAiO026962 AT envy DOT delorie DOT com> <201509122223 DOT t8CMNhaZ024482 AT envy DOT delorie DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > Another option here is to switch to a file format that's already > supported by lots of other languages, like XML or YAML. Then the > remaining work breaks down into: > > * Deciding on a schema for the data > > * converting pcb to read/write that schema > > Scripts wouldn't *need* to use pcb's parser, they could use any old > parser library, since the scripts already know what the parts of the > schema they're interested in look like. Read file, fiddle with the > parts you know, write file leaving everything else intact. Are there really an problems with the current file format that's hampering development?