X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Mailer:	exmh version 2.8.0 04/21/2012 with nmh-1.7+dev
X-Exmh-Isig-CompType:	repl
X-Exmh-Isig-Folder:	inbox
From:	"karl AT aspodata DOT se [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] schematic attributes
In-reply-to:	<6A7334BE-D0A5-4824-B3FC-800ADBE892F9@noqsi.com>
References:	<20220821141622 DOT A5836824697A AT turkos DOT aspodata DOT se> <63288ff-b013-eb67-cf40-56d6119e8cfa AT grinsen-ohne-katze DOT de> <20220824165958 DOT C92CB80724AC AT turkos DOT aspodata DOT se> <d8b9a31-c7e7-bc6-c719-6ed8a2a0eb1e AT grinsen-ohne-katze DOT de> <20220825181205 DOT F072C80724AA AT turkos DOT aspodata DOT se> <6A7334BE-D0A5-4824-B3FC-800ADBE892F9 AT noqsi DOT com>
Comments:	In-reply-to John Doty <jpd AT noqsi DOT com>
	message dated "Thu, 25 Aug 2022 15:45:22 -0400."
Mime-Version:	1.0
Message-Id:	<20220826104410.B792380724AA@turkos.aspodata.se>
Date:	Fri, 26 Aug 2022 12:44:10 +0200 (CEST)
X-Virus-Scanned:	ClamAV using ClamSMTP
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

John Doty:
> > On Aug 25, 2022, at 2:12 PM, karl AT aspodata DOT se [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> > 
> > The upper (gschem,gnetlist) doesn't have to know about what it is,
> > it is up to the backend to handle the xxxx's and document its use,
> But most attributes are already transparent to schematic capture and
> to the core netlister.
> > and the backend might prefer some other syntax than var=value.
> And if that’s what it prefers, that’s fine. Both geda and lepton have
> supported arbitrary, multi-line strings as attribute values for years.
> But old-fashioned var=value is also handy. gnet-spice-noqsi has its
> multiline macro attributes spice-prototype, spice-prolog, and spice-epilog,
> but it also uses file, model, and device. Macro expansion often picks up
> value, and it can pick up any other var=value, handy for attributes like
> l=0.4u (400 nm channel) on a MOSFET.
> So, the basic machinery is in place. With the right backend coding,
> it's easy to avoid the problems caused by overloading pinseq.

Soo, things are better than I thought, thanks for enlightning me.

> But the thing we lack is conventions. What are our standard device
> attributes? What, exactly, goes into a value attribute? We’re missing
> some things: I use spec attributes (like spec=5% 1/10W) in my designs.

You are correct, thanks for expressing this.
The lack of conventions hinders cooperations and sharing of projects.

Regards,
/Karl Hammar

- Raw text -