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=20161025;
        h=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-transfer-encoding;
        bh=p3L37yg9hFh59BB4OeNq/CPYecxZfy9jtWNWQuIikMo=;
        b=clGQzFV3xCtpcfGl57Fzirn9xAj/Tf2s7Y/lJ1E9rhvFgEViWApzRb2XEt1vzhilTF
         kvGUCwteTJamUrTJAHF/F88fKPgcCdM9qhLveYg7bifE2S9CmMq1Og+KEmXk+uIXU6Mw
         lhhXqgFVuYz7LiRy+DZp19i6ixNs5abOUp56hGPBk/ZF4F5I4XdjXvpYSZUcQy8liHhu
         LsxNTiMu0AKFF0D2XNa2GGR17pd7bI84f6pR5nsAme8YfoJbMPtujNZz2+wnyTjmjeL6
         ltZGvEomWxL0zYktsPZgLqDQVHRljAvrAnfc5TOCVKziXXXxWj8O3ar5YWNQ2mPoLOc+
         zEKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-transfer-encoding;
        bh=p3L37yg9hFh59BB4OeNq/CPYecxZfy9jtWNWQuIikMo=;
        b=qMW1T5G9SMD1SmUintZmlow8/4Wr0mD3e72ngdG3+wkw66qp0bzMV0qCuyX+S10v43
         XCUT0Ke06nj8PjBbzyPADweyxD36tUD00bHVfTzWu/Jp/OFC5Vr9MWLoyc0TXzcpulNy
         sNOdH0zl0vrIyliTJA5N5VDVIThiLwTCuN6xLACTDtWVejKOhB2dybgpzAw4aEw780pL
         SCf7vG85Mu5LznD/6TeWAION7jK9QhPjEZC6GNKS48ewB2RD1jS8kvfSv20avXXr3otU
         /eeKwgmcEi9bnb2wdbWEv8dDJ53VWmnlGjbnd0ZvdG3xdczpEjBjrpxSW8z2VSS2dDh6
         yAIw==
X-Gm-Message-State: AKGB3mJlhF36mOv0IkLfRKbFeF9J5z4xViz73D/7Uz5NNQ6k1RwUbM0l
	dKqvu+tLTuLrB1b6+aLe4+bbkw==
X-Google-Smtp-Source: ACJfBovVGxVS+aIYkHHxP/pDjY+mX+Fv3eLDZhf0p0RvKkpiD3UdcfVN1cYaI3c/r6Wzc/jQJfmD7A==
X-Received: by 10.46.84.27 with SMTP id i27mr26443718ljb.87.1514925128962;
        Tue, 02 Jan 2018 12:32:08 -0800 (PST)
Date: Tue, 2 Jan 2018 21:32:05 +0100
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] why pinnumber in sym pins?
Message-Id: <20180102213205.4565128f84cb6f27ef88033d@gmail.com>
In-Reply-To: <alpine.DEB.2.20.1801022021340.14184@nimbus>
References: <20171226122009 DOT 366BF804CEDE AT turkos DOT aspodata DOT se>
	<alpine DOT DEB DOT 2 DOT 20 DOT 1801022021340 DOT 14184 AT nimbus>
X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

On Tue, 2 Jan 2018 20:30:49 +0100 (CET)
Roland Lutz <rlutz AT hedmen DOT org> wrote:

> On Tue, 26 Dec 2017, karl AT aspodata DOT se wrote:
> > Why must one have a pinnumber attribute for each pin i a sym file:
> > http://wiki.geda-project.org/geda:master_attributes_list#pinnumber
> 
> The pin number is the main identifier of a pin inside a component.
> Having a pin without an identifier would only make sense if the behavior
> of that pin is defined in another way, and you never need to refer to
> that pin by its identifier.

Yes but ...

> > Wouldn't it be useful to allow  to have just a function (pinlabel)
> > attached to the pin without knowing which pinnumber it will end up on ?
> 
> You would still need some way of mapping the function to the pinnumber.

The default then not pinnumber identifier is available could be pinlabel or default could be to used pinnumber but no pinlabel in symbols.

Schematics are read by human so it make sense to use pinlabel as identifier.

To make symbols with pinnumber but no pinlabel might be a solution and then there is a need for a difference pinnumber may be hidden while pinlabel is visible?