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=date:from:to:subject:message-id:mail-followup-to:references
	:mime-version:content-disposition:content-transfer-encoding
	:in-reply-to:user-agent;
	bh=jjaFLl2p5lPKXrC5C3kCbbBUGozSYTM+Mxd8tIpsV6Y=;
	b=qPZUj8gHAbaf/cGFwxPtwFZjlLJQEAsQa9Itx+yV0vaU9cejjQZzjVboQiSxBC7NO7
	egQRbhZ8ws+9P1PH6nCx6d8fzF8T/fOUA3tmIo9It6nCnRvVj/msRaQhZJaOcX1nzW1+
	93PJJB3vOInUePpFq617jojzxNKivwksbrPFyzO9UpNpWbxbt76onwbahdGnq7PqcNCv
	XWBYgoET9xl5qsKvP/G8mnMjZHAhyn8n/Ql2PaxQ287zovCUeJfEQfvQogv+53l1omG+
	IaKrWVWA9gkytSfEJNzT1dgEMdGC/I2e2cacjvbOO6Oxa2+UeCY0aRfP1VndLb+ZpnJQ
	eibw==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to
	:references:mime-version:content-disposition
	:content-transfer-encoding:in-reply-to:user-agent;
	bh=jjaFLl2p5lPKXrC5C3kCbbBUGozSYTM+Mxd8tIpsV6Y=;
	b=AgzGzqUqfUdlaY4iBZi2knBGIQ+vA6a5juNMe1wWmw9i4iBu+RVtS+LkW1WDsUmvm2
	HTHBzuwt3GkfDzhkyj6jxLPeZJE9hjHLKdSHrxJfMwKVfqP1G9Y9hv36EyWVlVqIm4Et
	iio4u5606OgeSVU4OfeILmkeyi6C6k4LYMtH3S0n16JUWmgXThEUF3W8k54b3Elcl171
	omFfDUC/+yr7a8mxg1ESP1aswRwAX45a91v2xIKJuBKCHnxw5b+vTybBgl/5LUNWa0U+
	Jgq/4iB6ZHfPXYYCAI/VGjGdpNziZILtaE3zlxdRR1iWZNV8f+D8KNLcJFTw1giQx+IW
	rvOw==
X-Gm-Message-State:	AE9vXwM/4HOfI63WntgX0ECqmqgc/pdseMzM7VsOygy0F0eHD/4p9Nc+VsVAtuANlS4Smw==
X-Received:	by 10.25.205.69 with SMTP id d66mr2468045lfg.127.1473512883484;
	Sat, 10 Sep 2016 06:08:03 -0700 (PDT)
Date:	Sat, 10 Sep 2016 16:08:00 +0300
From:	"Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Can an attribute be attached to text for later
	inclusion in gnetlist backend?
Message-ID:	<20160910130800.GB2549@localhost.localdomain>
Mail-Followup-To:	geda-user AT delorie DOT com
References:	<20160823053301 DOT 865f671a1b40b5a422e59ce7 AT gmail DOT com>
	<da433c1d-c711-e0d8-f9ff-a6e843bfe266 AT sbcglobal DOT net>
	<AB0B2DAD-9075-4AEC-B33E-A57DA050B079 AT noqsi DOT com>
	<CAGde_xOYrkv-4eWyR4OOTT+XQMPcr4MxmT1xomB9uCneZBCT6A AT mail DOT gmail DOT com>
	<20160824185818 DOT GD14293 AT localhost DOT localdomain>
	<CAGde_xNfx_VmpWTm6EwHac2QaKQCRefs1cKK=s9gE8OOuMiWdA AT mail DOT gmail DOT com>
	<20160831221409 DOT GA2585 AT localhost DOT localdomain>
	<CAGde_xMDpUFy5P05Mg+zmzDtvbshvZAghR13F4UkSxxMqtw7yw AT mail DOT gmail DOT com>
	<20160906213426 DOT GA10224 AT localhost DOT localdomain>
	<5A8E8F14-D4A4-412E-A412-7D97A0306C7B AT noqsi DOT com>
MIME-Version:	1.0
In-Reply-To:	<5A8E8F14-D4A4-412E-A412-7D97A0306C7B@noqsi.com>
User-Agent:	Mutt/1.5.23 (2014-03-12)
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 Tue, Sep 06, 2016 at 04:30:10PM -0600, John Doty wrote:
> 
> On Sep 6, 2016, at 3:34 PM, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> 
> > Having been thinking before of
> > all the ambiguous attribute names we have in geda where each
> > gnetlist backend has its own vision on their use, now I think
> > every one of them being non-compatible with others should have a
> > different backend-specific name.
> 
> The way I do it in gnet-spice-noqsi is to have spice-specific attributes spice-prototype, spice-prolog, and spice-epilog. Those feed a simple macro expander that can *refer* to the old overloaded attribute names. There are built-in defaults for the spice-prototype attribute selected by the device attribute.
> So, for example, the default prototype for device=RESISTOR is
> 
> R? %pinseq value@ model-name@ spice-args@ w= l= area= temp=“
> 
> This does the following:
> 
> 1. Insures the refdes starts with R.
> 
> 2. Uses pinseq to order the connections, as in the past.
> 
> 3. Uses the value attribute for the resistance, as in the past.
> 
> 4. Picks up other optional attributes.
> 
> The user can override this with a spice-prototype attribute to
> get any output desired. This approach avoids getting in the way
> of other back ends, while most often doing the “right thing” by
> default.

Yes, we can go this way, and even accomodate other backends to
support such (or similar) attribute using. Anyway, using of
namespaces would not harm. Moreover, we could establish an
attribute priority, e.g., use first spice-device= (or
spice:device=, or spice::device=) if it is defined, and device= if
it is not.

-- 
  Vladimir

- Raw text -