kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #06316
Re: Sweet parser
On 03/21/2011 02:02 PM, jean-pierre charras wrote:
> Le 21/03/2011 18:58, Dick Hollenbeck a écrit :
>> 2)))))))))))))))))
>>
>> 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.
>> Thanks,
>> Dick
>>
>
>
> 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
PIN::NUMBER.
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
"description".
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.
Dick
Follow ups
References
-
Sweet parser
From: Dick Hollenbeck, 2010-12-30
-
Re: Sweet parser
From: Wayne Stambaugh, 2010-12-30
-
Re: Sweet parser
From: Dick Hollenbeck, 2010-12-30
-
Re: Sweet parser
From: Wayne Stambaugh, 2010-12-30
-
Re: Sweet parser
From: Dick Hollenbeck, 2010-12-30
-
Re: Sweet parser
From: Dick Hollenbeck, 2011-01-03
-
Re: Sweet parser
From: Dick Hollenbeck, 2011-01-03
-
Re: Sweet parser
From: Wayne Stambaugh, 2011-01-03
-
Re: Sweet parser
From: Dick Hollenbeck, 2011-02-14
-
Re: Sweet parser
From: Dick Hollenbeck, 2011-02-28
-
Re: Sweet parser
From: Dick Hollenbeck, 2011-03-21
-
Re: Sweet parser
From: jean-pierre charras, 2011-03-21