X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Sun, 21 Aug 2022 22:50:49 +0200 (CEST)
From:	Roland Lutz <rlutz AT hedmen DOT org>
To:	"karl AT aspodata DOT se [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject:	Re: [geda-user] schematic attributes
In-Reply-To:	<20220821141622.A5836824697A@turkos.aspodata.se>
Message-ID:	<63288ff-b013-eb67-cf40-56d6119e8cfa@grinsen-ohne-katze.de>
References:	<20220821141622 DOT A5836824697A AT turkos DOT aspodata DOT se>
MIME-Version:	1.0
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 Sun, 21 Aug 2022, karl AT aspodata DOT se [via geda-user AT delorie DOT com] wrote:
> lepton:
>   net (port) symbols (in subsheet) can have a net attr.
>   symbol attribute
> geda:
>   portname
>   netname in net (power) symbols
>
> As a user, I believe that it is important that the schematics I
> make can be used in both programs.

gEDA/gaf is and will be fully downwards-compatible, so any schematic that 
worked with an older version of gEDA/gaf will work with a newer version, 
as well.  lepton-eda somewhat breaks that, but as long as you check the 
netlist output for problems, you should be fine.  So the attributes used 
with gEDA/gaf 1.9.2 (net=, in this case) can be used as a compromise.


> Is it time to make a clean break from the "old" attributes and
> define a new set

Oh no, please don't!

https://xkcd.com/927/


> So far I know of theese use cases for attributes:
> SPICE, gnucap, simulations
> pcb rnd-pcb
> bom
> DRC
> which seems to boil down to how netlist treats the attributes.

My preferred approach is to allow prefixing attributes with their 
respective domains (pcb:footprint=, spice:device=, and so on) but 
otherwise keep the existing semantics.

Roland

- Raw text -