← Back to team overview

kicad-developers team mailing list archive

Re: Sweet parser


Le 21/03/2011 21:48, Dick Hollenbeck a écrit :
On 03/21/2011 02:02 PM, jean-pierre charras wrote:
Le 21/03/2011 18:58, Dick Hollenbeck a écrit :

Jean-Pierre or anyone else,

Anyone have and second thoughts on the need to continue with both a pin name
AND a pin number, going forward?   I cannot remember why we need both.

Please, can you tell us more about your thoughts ?
Just because usually a pin have a name (a comment) and a pin number (the links to a footprint pad)

My question is more about PIN::NAME than PIN::NUMBER.  I fully understand
I know you know, of course.

My motivation is to keep only what is needed, and make sure that which is
kept is identified most appropriately.  So I am asking for a 3 sentence
education on pin names, that is all.

To me a name is a very exact description, so if this PIN member is really
just a comment, maybe that is all the education I need.

Basically, the question is, how is the pin name used?

If it turns out to be only a description, I might suggest we call it

I am not in a position to drive change, until I am in a position of knowledge.

Thanks for the help  (I know grepping the code would tell me the same
thing), but this saves a little time.


Pin name is, in fact, actually a pin description, and currently is just a comment.

About pin "numbers" (currently a 4 characters identifier) I believe an enhancement in Eeschema could be the support of pins having multiple pin numbers.
I see 2 cases:
-Power pins in large ICs:
 they have 100 or more GND, VCC .. pins.
 In schematic an enhancement could be: put only one pin having one pin name (or description) and a lot of pin numbers.
-"Bus pins"
 The is in fact a similar case: one pin having many pin numbers.
 Useful for components like memories and microprocessors to handle data bus and address bus with only 2 pins.
the difference between these pins is mainly for netlist generation.

In library files format and load/save functions, just allow the ability to store more than one pin number per pin.
The cost is low.

Jean-Pierre CHARRAS

Follow ups