X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 98.110.213.70 X-Authenticated-UID: jpd AT noqsi DOT com From: John Doty Content-Type: multipart/alternative; boundary="Apple-Mail=_67BBD0DF-BABA-4320-B9C6-A1CE8B5CBB25" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: [geda-user] schematic attributes Date: Thu, 25 Aug 2022 15:45:22 -0400 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> <20220825181205 DOT F072C80724AA AT turkos DOT aspodata DOT se> To: "Girvin Herr (gherrl2 AT fastmail DOT com) [via geda-user AT delorie DOT com]" In-Reply-To: <20220825181205.F072C80724AA@turkos.aspodata.se> Message-Id: <6A7334BE-D0A5-4824-B3FC-800ADBE892F9@noqsi.com> X-Mailer: Apple Mail (2.3696.120.41.1.1) 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=_67BBD0DF-BABA-4320-B9C6-A1CE8B5CBB25 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Aug 25, 2022, at 2:12 PM, karl AT aspodata DOT se [via = geda-user AT delorie DOT com] wrote: >=20 > 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=3Dvalue. >=20 And if that=E2=80=99s what it prefers, that=E2=80=99s fine. Both geda = and lepton have supported arbitrary, multi-line strings as attribute = values for years. But old-fashioned var=3Dvalue 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=3Dvalue, handy for attributes like l=3D0.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. But the thing = we lack is conventions. What are our standard device attributes? What, = exactly, goes into a value attribute? We=E2=80=99re missing some things: = I use spec attributes (like spec=3D5% 1/10W) in my designs. John Doty Noqsi Aerospace, Ltd. jpd AT noqsi DOT com --Apple-Mail=_67BBD0DF-BABA-4320-B9C6-A1CE8B5CBB25 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8


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=3Dvalue.


And if that=E2=80=99s what it prefers, = that=E2=80=99s fine. Both geda and lepton have supported arbitrary, = multi-line strings as attribute values for years. But old-fashioned = var=3Dvalue 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=3Dvalue, handy for attributes like l=3D0.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. = But the thing we lack is conventions. What are our standard device = attributes? What, exactly, goes into a value attribute? We=E2=80=99re = missing some things: I use spec attributes (like spec=3D5% 1/10W) in my = designs.

John Doty              Noqsi = Aerospace, Ltd.

jpd AT noqsi DOT com




= --Apple-Mail=_67BBD0DF-BABA-4320-B9C6-A1CE8B5CBB25--