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:in-reply-to:references:mime-version
         :content-type:content-transfer-encoding;
        bh=t7u2a2RHZv/tw32s3PIJ2rqcz/TKeGTYz++PLVmQFfc=;
        b=RaFmnApNK39B4bYYRfh+XlxViWYygMxviR5FiL2O/9fSJw+h0rWVcr7n+071h3ulVR
         qwVdM4+hSzpE0MwcHBdJeVz0LksYO5T0yMJ7aRCUJ4mU2zvCw9Vb3hOT+DuNYfZF7zHd
         eWdqEfqD1eP2qrBACR8xBIf1TaTS3sNEwbI3gWGsg3Msskvxeroi4qE9c8oVAyN6uCiD
         mn9wgnen0Xp5sc/iNu3J51f1ALiE2jSovg/8SxuMJrx+LpUzg/exVvDeuzvTdGjOroRv
         cGkRsg1SRfWZGdx3sjdrEO/lcZCFF3s/2/9xxCy82uePMcWVfrnZt1w+PVrONkB4FnBE
         GSBw==
X-Received: by 10.194.80.71 with SMTP id p7mr30754667wjx.83.1444680410782;
        Mon, 12 Oct 2015 13:06:50 -0700 (PDT)
Date: Mon, 12 Oct 2015 22:06:49 +0200
From: "Nicklas Karlsson (nicklas DOT karlsson17 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] A lesson from gnet-makefile
Message-Id: <20151012220649.da6dfea4f040e5fb8300ae9c@gmail.com>
In-Reply-To: <1042003D-82E2-40F0-AB60-8186580C46AD@noqsi.com>
References: <1042003D-82E2-40F0-AB60-8186580C46AD AT noqsi DOT com>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
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

> Folks,
> 
> I had thought that the lack of a way to access attributes other than netname= on a net via gnetlist was a serious barrier to the back end writer. However, for gnet-makefile.scm  I find myself using the attributes of the attached symbols as a rich source of information about the net. Is this perhaps the best approach anyway?
> 
> Nets in a schematic represent collapsed topology, not geometry or even the complete topology. The layout system is responsible for these things. A schematic doesn’t capture the relationships between the net segments. Some paths on a net may carry large currents, but others may not. Pairs of nets may represent balanced transmission lines.
> 
> But, suppose instead that we had a pin attribute that said “this pin may draw three amps”. The netlister could then deduce which paths on a net need extra conductor.
> 
> Suppose a resistor had an attribute that meant  “100 ohm shunt terminator”. Imagine a component with a pair of pins identified by an attribute as a differential input. Put them on the same pair of nets, and the netlister could deduce that the pair is a balanced transmission line and the the resistor needs to be close to the input.
> 
> Of course, we’d need a layout program that could accept this info.
> 
> John Doty              Noqsi Aerospace, Ltd.
> http://www.noqsi.com/
> jpd AT noqsi DOT com

As I understand it you want to assign attributes to pins instead of nets.

A net is only allowed to have one driver and will get the voltage of the driving pin and from this voltage a suitable clearance may be selected. For current it will be the other ends. It might work but I still think net names are useful sometimes, maybe it would be useful to use the driving pin to assign the net name, if this is simple to implement I guess it would be worth a try.