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 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] Difference between attached and detached attributes From: John Doty In-Reply-To: Date: Sat, 18 Jul 2015 17:41:25 -0600 Message-Id: References: <55A813B5 DOT 4040609 AT sbcglobal DOT net> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t6INfVFG006306 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 Jul 18, 2015, at 4:09 PM, Roland Lutz wrote: > You can delete an inherited attribute by > attaching an attribute with the value "unknown" to the component. That depends a bit on the gnetlist back end. The primitive gnetlist:get-all-package-attributes yields #f (Scheme’s token for falsehood) for a missing attribute. The derived gnetlist:get-package-attribute substitutes “unknown” for this. Back ends generally use gnetlist:get-package-attribute and interpret “unknown” as the token for a missing attribute. That is not, however, required behavior. Things get more interesting if you have multiple symbols for one refdes. The default behavior is difficult to predict (that’s what I call the “attribute censorship bug”). If you’re using my censor-fix.scm, a missing attribute does not conflict with an attribute associated with a different symbol, but an attribute of “unknown” will conflict unless all symbols agree that it’s “unknown". John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com