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 <jpd AT noqsi DOT com> 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> <d8b9a31-c7e7-bc6-c719-6ed8a2a0eb1e AT grinsen-ohne-katze DOT de> <20220825181205 DOT F072C80724AA AT turkos DOT aspodata DOT se> To: "Girvin Herr (gherrl2 AT fastmail DOT com) [via geda-user AT delorie DOT com]" <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] <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 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br = class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div = class=3D"">On Aug 25, 2022, at 2:12 PM, <a = href=3D"mailto:karl AT aspodata DOT se" class=3D"">karl AT aspodata DOT se</a> [via <a = href=3D"mailto:geda-user AT delorie DOT com" = class=3D"">geda-user AT delorie DOT com</a>] <<a = href=3D"mailto:geda-user AT delorie DOT com" = class=3D"">geda-user AT delorie DOT com</a>> wrote:</div><br = class=3D"Apple-interchange-newline"><div class=3D""><span = style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: = 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; = letter-spacing: normal; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: none; float: none; = display: inline !important;" class=3D"">The upper (gschem,gnetlist) = doesn't have to know about what it is,</span><br style=3D"caret-color: = rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: = normal; font-variant-caps: normal; font-weight: 400; letter-spacing: = normal; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, = 0); font-family: Helvetica; font-size: 12px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none; float: none; display: inline !important;" = class=3D"">it is up to the backend to handle the xxxx's and document its = use,</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: = Helvetica; font-size: 12px; font-style: normal; font-variant-caps: = normal; font-weight: 400; letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: = none;" class=3D""></div></blockquote><br class=3D""></div><div>But most = attributes are already transparent to schematic capture and to the core = netlister.</div><div class=3D""><br class=3D""></div><blockquote = type=3D"cite" class=3D""><span class=3D"" style=3D"float: none; display: = inline !important;">and the backend might prefer some other syntax than = var=3Dvalue.</span><br class=3D""><br class=3D""></blockquote><div = class=3D""><br class=3D""></div>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.<div class=3D""><br class=3D""></div><div = class=3D"">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.</div><div class=3D""><br class=3D""><div class=3D""> <span class=3D"Apple-style-span" style=3D"border-collapse: separate; = border-spacing: 0px; font-variant-ligatures: normal; = font-variant-east-asian: normal; font-variant-position: normal; = font-weight: normal; line-height: normal;"><div style=3D"word-wrap: = break-word;" class=3D""><span class=3D"Apple-style-span" = style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, = 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; = font-variant-ligatures: normal; font-variant-caps: normal; = font-variant-east-asian: normal; font-variant-position: normal; = font-weight: normal; letter-spacing: normal; line-height: normal; = text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; = widows: 2; word-spacing: 0px;"><p style=3D"margin: 0px;" class=3D""><font = face=3D"Helvetica" size=3D"3" style=3D"font-style: normal; = font-variant-caps: normal; font-weight: normal; font-size: 12px; = line-height: normal; font-family: Helvetica;" class=3D"">John Doty<span = class=3D"Apple-converted-space"> <span = class=3D"Apple-converted-space"> </span><span = class=3D"Apple-converted-tab"> <span = class=3D"Apple-converted-space"> </span></span></span>Noqsi = Aerospace, Ltd.</font></p><p style=3D"margin: 0px;" class=3D""><a = href=3D"mailto:jpd AT noqsi DOT com" class=3D"">jpd AT noqsi DOT com</a></p><br = class=3D"Apple-interchange-newline"></span></div></span><br = class=3D"Apple-interchange-newline"> </div> <br class=3D""></div></body></html>= --Apple-Mail=_67BBD0DF-BABA-4320-B9C6-A1CE8B5CBB25--