X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sun, 10 Jan 2016 22:19:29 -0500
Message-Id: <201601110319.u0B3JTVl025695@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to:
	<CAC4O8c8iQnuy2L8QG=absBhnUTuVRj-jJyVNhoqeSiPmiT0gWw AT mail DOT gmail DOT com>
	(geda-user AT delorie DOT com)
Subject: Re: [geda-user] A new PCB file format - modular system
References: <5692CBD5 DOT 3020101 AT prochac DOT sk> <CAC4O8c8iQnuy2L8QG=absBhnUTuVRj-jJyVNhoqeSiPmiT0gWw AT mail DOT gmail DOT com>
Reply-To: geda-user AT delorie DOT com


> What surprises me is that it looks like you were able to do
> everything with PCBType.  I don't remember the gruesome details now
> but last time I tried to make the existing parser work independent
> of pcb I ended up with the impression that PCBType didn't reflect
> everything that goes in pcb files -- close but not quite everything.

Note that one of the messy and probably written rules about hid is -
the hid module can do whatever it wants with core data and functions,
but the core can only access the hid module via the published API.

So if an importer/exporter needs more data than PCBType, it can just
reach in and get it.