X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Tue, 1 Sep 2015 12:41:54 +0200 (CEST) X-X-Sender: igor2 AT igor2priv To: "Levente (leventelist AT gmail DOT com) [via 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] full perl parser for pcb files? In-Reply-To: Message-ID: References: <20150901094810 DOT 16370 DOT qmail AT stuge DOT se> 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, 1 Sep 2015, Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: >Is this written in Perl? C + yacc + lex >Is there any documentation for PCB internals? The PCB code is commented well at strategic places. Some parts use strange paradigms, but most parts are pretty straightforward to understand. At least this is my experience hacking pcb-rnd. Also, most parts of the PCB source doesn't suffer from the spaghetti effect and you can go there to check/fix things locally without first needing to understand the whole class hierarchy or type system or whatnot. Names are good too, so it's usually easy to guess a keyword to search for. Regards, Igor2