X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <55EC6021.70609@xs4all.nl> Date: Sun, 06 Sep 2015 17:47:45 +0200 From: "Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com]" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] Using parse_l.y etc. for parsers for other languages (via SWIG) References: <20150906154849 DOT 2449a717 AT jive DOT levalinux DOT org> In-Reply-To: <20150906154849.2449a717@jive.levalinux.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com Lev (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > On Sat, 5 Sep 2015 16:51:37 -0800 > "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" > wrote: > > >> Peter suggested using the parser in pcb rather than rewrite in perl. >> >> I had a look and I think it's not a bad idea. Would get a faster >> parser and not too painful I think. I'm considering using SWIG >> with some functions to iterate over PCBType contents to rebuild >> the lists perl-side. As a bonus you would get parsers for lots of >> languages for cheap. It would be easiest to do this in-tree. >> >> Would this work for what you have in mind on your end? >> > I think it is a good idea to use something that is well written. I'm okay > with SWIG. However, it doesen't have to be perl. So yes, if this is towrds the > goal of creating a parser, I think this is a good way. > > Btw, it has a name now, it is called Apollon-PCB. > > I crated a github project, as my server went down. So I can grant you (and > anyone) commit access. > > https://github.com/leventelist/apollon > > I look for other developers who can contribute to this project. > > As the readme states, I want to integrate this into pcb, OR create a brand new > project, and use as much code as we can from gEDA/pcb. > > The schema is changed a bit. I removed hard wired attributes, and created an > attribute table. > > Lev > > > Hi Levente, You could ask for an account on upstream pcb.git and do your work in a branch named like "home/levente/apollon", or any other branch name starting with "home/levente/". This way we can have the best of both worlds ;-) Easier for you to cherry pick commits that get added after branching, and vice versa. Kind regards, Bert Timmerman