X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 X-Authenticated-UID: jpd AT noqsi DOT com From: John Doty Content-Type: multipart/alternative; boundary="Apple-Mail=_CE4198DC-C3D0-4647-9439-1E91B2CD0012" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [geda-user] [pcb] mainline: redundant attributes: bug or feature? (fwd) Date: Wed, 16 Aug 2017 13:52:26 -0600 References: To: geda-user AT delorie DOT com In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3273) 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 --Apple-Mail=_CE4198DC-C3D0-4647-9439-1E91B2CD0012 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Aug 16, 2017, at 9:24 AM, DJ Delorie wrote: >=20 >=20 > Remember, folks, the main purpose of this thread is to talk about > duplicate attributes *in pcb*. Nobody has suggested any changes to > gschem. >=20 > In pcb you'd need unique names, like comment1, comment2, etc. This = has > always been the case so nothing new. >=20 > The only time it would matter is when you're importing a schematic = into > pcb, and you want all the attributes copied to the element - but that > never supported duplicates anyway. >=20 The place where gschem=E2=80=99s capabilities get matched to downstream = needs is in the gnetlist back ends. It seems to me perfectly reasonable = to discuss conventions for transmitting information downstream along = with the specifics of how these would work for downstream tools like pcb = through the gnetlist back ends. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_CE4198DC-C3D0-4647-9439-1E91B2CD0012 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On Aug 16, 2017, at 9:24 AM, DJ Delorie <dj AT delorie DOT com> = wrote:


Remember, folks, the main purpose of this = thread is to talk about
duplicate attributes *in pcb*. =  Nobody has suggested any changes to
gschem.

In pcb you'd need unique names, like comment1, = comment2, etc.  This has
always been the case so = nothing new.

The only time it would matter = is when you're importing a schematic into
pcb, and you = want all the attributes copied to the element - but that
never supported duplicates anyway.


The place = where gschem=E2=80=99s capabilities get matched to downstream needs is = in the gnetlist back ends. It seems to me perfectly reasonable to = discuss conventions for transmitting information downstream along with = the specifics of how these would work for downstream tools like pcb = through the gnetlist back ends.

John Doty              Noqsi = Aerospace, Ltd.

http://www.noqsi.com/

jpd AT noqsi DOT com

= --Apple-Mail=_CE4198DC-C3D0-4647-9439-1E91B2CD0012--