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=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=RpqYZf71idw5J8NVwRo3a+3h6/aKhIkLjroXpNqRrfM=;
        b=JoT9bTb7Z2w8/qWPoIUcXsEk9wZesqqT/ptVGaI0wvTPehhPBYmxuNGgvk+bempwwC
         FHoHZFXqP42upP2yz7WUufdBZE7t4Gr7bfcX42Jlm+LnCAnz6NQscSSkCn+YOhc/7dDo
         dm7z7CR5zcQc3t+ZvcqDvDX+5vtywkOsH5QGCEz8SfbZl12CbsgW3xFjCPX44jsK43a4
         qF/dIXr7/DY2BlSQrzmlAy6JVj/KxMw/UEJGybbwCOV30HcrZdYgWJbFG9cMNk4YL0vu
         gpjwr7Ra7fUUlADdWa7PnS5InAWnBWsSeTOjtQdO33tkd6+eWfd0ptprppb+AwY1Zo/G
         ZhQg==
MIME-Version: 1.0
X-Received: by 10.194.109.97 with SMTP id hr1mr11393258wjb.38.1442093350740;
 Sat, 12 Sep 2015 14:29:10 -0700 (PDT)
In-Reply-To: <201509120239.t8C2dAiO026962@envy.delorie.com>
References: <CAC4O8c_XFEAgyrokrwwavB0C+OjWXCB5xptkVwMx2i_t960qFg AT mail DOT gmail DOT com>
	<201509120239 DOT t8C2dAiO026962 AT envy DOT delorie DOT com>
Date: Sat, 12 Sep 2015 13:29:10 -0800
Message-ID: <CAC4O8c_hq9WSaRtv1dUZLyFW-UaPBs-95JGB94EevdiLp8gQtg@mail.gmail.com>
Subject: Re: [geda-user] shortest way towards parsing .pcb files outside pcb
From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
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 Fri, Sep 11, 2015 at 6:39 PM, DJ Delorie <dj AT delorie DOT com> wrote:
>
>> Is this something that's about to happen?  If so I'll stop working on
>> wrapping the parser from PCB.
>
> It's not clear to me what the advantage of this would be.  Most of the
> things that deal with pcb structures are either scripts that use text
> processing (which could use a standalone parser), or pcb plugins which

The standalone parser would be a much slower reinvention, so it was
suggested to use the one already in pcb.  The idea is to ship language
modules that people can use to parse .pcb from their own scripts.

> have access to the full pcb data structure anyway.
>
> If we were to add xorn as a scripting engine to pcb, it would need to
> be integral to the core data structures so the scripts could affect
> the live data, which would be a huge task.  Add xorn just to be a

This is a big job and I think Igor has already done it, I could not
bear to reinvent it again.  I just want a full .pcb version from
scripts.
Should pcb-rnd ever merge it would complement that work by providing a
simpler form of access forpeople who want to make scripts that don't
need live interaction.

> reader/writer for pcb doesn't really add anything.
>
> Given how many discussions we've had about improving the data
> structure itself (which would be a huge job due to the amount of code
> that knows about it, even just switching to a xorn data), is this a
> path to simplify that?

Yes it's a small step (see previous posts).