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=fastmail.com; h=
	content-transfer-encoding:content-type:date:from:in-reply-to
	:message-id:mime-version:references:reply-to:subject:to
	:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=JYEDP4
	eVs3C/uXstcJlzUvL/7cWYl1Fcu2YjdVlY3Sc=; b=EcPAYHgNeTX0pRehrbZrnI
	TezyBUoRa0/vA30/gwuJg5qkul/xo8vZhE6bFKC/KiTc44RY8wj5MpWbamevXi2s
	rrUg3muLKwPw8rhWRm0C5b0MvBj60XcneUBdTdpjElE1RJxaYJUCqJ+9fnUNvhn+
	RXbnf50mKpQ5qqSAJdXTzMYXJj2d+Afna/f9CI6K3nZAUT7AxHYV1ulyTTe36C+G
	6Jq/rewFZwTNVuVgI8lQgHWwyn8ogtRGaxvWRO/FE7hR5dFKB/F0Kj/8u2oXAjfO
	N4M5CDLuxyPK/IpvjcH423oTQXEkRId7FEVMsw3csEGfau36Oj4LCIDxiAr/m5yA
	==
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:reply-to:subject:to:x-me-sender:x-me-sender:x-sasl-enc
	:x-sasl-enc; s=fm1; bh=JYEDP4eVs3C/uXstcJlzUvL/7cWYl1Fcu2YjdVlY3
	Sc=; b=GztPTxAQdCKaMPYyXL2wu32ZfPbTvQso9x4qWgjXzyS6wxLCO6hipOmTB
	1OkuLBMHsKGlt0TKgL5qfdE0Q8V10Tk/YKXL9od56FzYHxrBjngFSvn//tAOCzNb
	s9lbDE8zd7n88LH3NnFIXPnghD0myke7OCObWc8rkfifyXw5SmaKZZERKFIMA0OL
	tXe6/rEqZvh/i9pixyIwyPQBmV2Q/rFMRQXHm7pfaifXZfczkIfzTntG/oWigTsu
	ImrMGV8WaLZR1J04xz/SX/k6HiQztXv6hiUhWK8h7NOmKqEs6e5ujFiRkNwUz1HV
	4keD4FTefTpjSJ+tJopzaVOT2MtEg==
X-ME-Sender:	<xms:6ZaUWYKXOAYwrVze3Yp6ADr2poN_Qomu20IneIu2Lzx6uilFtrq66g>
X-Sasl-enc:	jeYDGMNpXG7o5RYcgrku7iA5qBMHaUE+4qUEq4R8vYhi 1502910185
Subject:	Re: [geda-user] [pcb] mainline: redundant attributes: bug or feature?
	(fwd)
To:	geda-user AT delorie DOT com
References:	<alpine DOT LRH DOT 2 DOT 01 DOT 1708160810170 DOT 3058 AT homer12 DOT u DOT washington DOT edu>
From:	"Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<d36de00d-9a5e-c856-c78c-cbe28a14122d@fastmail.com>
Date:	Wed, 16 Aug 2017 11:56:55 -0700
User-Agent:	Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101
	Thunderbird/52.2.1
MIME-Version:	1.0
In-Reply-To:	<alpine.LRH.2.01.1708160810170.3058@homer12.u.washington.edu>
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

On 08/16/2017 08:15 AM, Frank Miles (fpm AT u DOT washington DOT edu) [via 
geda-user AT delorie DOT com] wrote:
> On 08/14/2017 10:28 PM, Nicklas Karlsson 
> (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
>>> I suspect my thoughts were this: the user API should require/expect
>>> unique keys (hence get-by-value) but the low level stuff should be able
>>> to preserve (erroneous) redundant keys when loading/saving a *.pcb 
>>> file.
>>> Making load/store git friendly is a goal in pcb.
>> Attribute with same name added several times may in sort of be 
>> interpreted as a list of values. In gschem it is possible to add 
>> several attributes with same name but it never make sense and it's 
>> not possible to know for sure which value is used.
> Greetings,
> As a user, I might add my 2-cents to this discussion by saying that I 
> use multiple instances of the "Comment" symbol attribute in my 
> schematics. I would hate to see this capability be removed. Comment 
> attributes to not span multiple text lines. Therefore, I need to add 
> as many "Comment" attributes as I need lines of text.
>
> Another item may be that earlier someone posted that only the first 
> instance of an attribute is used and subsequent instances are ignored. 
> Why not the last instance is used and previous instances are ignored, 
> as in many other configuration scripts. That way the latest version 
> would be used and the system would be more forgiving. A warning, not 
> an error should suffice.
>
> Girvin Herr
>
> ----------------------------
>
> I also make heavy use of multiple "Comment" entries for a given 
> component.
>
> An even nicer alternative (for me) would be to enable custom attribute 
> types.
> Currently I use these entries to add hooks that tie entries in our 
> local component
> database with the schematics - a custom attribute type would be cleaner.
>
>     -Frank
Frank,
Actually, I think you can make up your own attribute names, if that is 
what you are asking by "attribute type". I did it a while back when I 
wasn't satisfied with the single "Device=" or "Value=" and wanted more 
info like "Power=", "Tolerance=", etc. The attribute name entry box is a 
list of attributes but it starts blank and one can enter any name one 
wishes, within reason. However, gsymcheck barfed on my new attribute 
names. It only supports the canned attribute names. So, if you don't use 
gsymcheck, then add your own attributes.

Devs: It would be nice if gsymcheck would allow new names, or maybe 
default with a warning and allow a command line option to turn such 
warnings off. I would like to make a script to use gsymcheck to test all 
my symbols before packaging them, but that is not possible as it stands, 
because it returns non-0 on those unknown attribute errors.

HTH.
Girvin Herr

- Raw text -