Re: gEDA-user: PCB format wishlist

[John Doty <jpd@xxxxxxxxx>]

On Sep 5, 2010, at 7:10 PM, DJ Delorie wrote:

> 
>>> We are NOT going with another position-determines-meaning file format.
>> 
>> Why?
> 
> Consider the parser for the PIN object:
> 
> Pin [rX rY Thickness Clearance Mask Drill "Name" "Number" SFlags]
> Pin (rX rY Thickness Clearance Mask Drill "Name" "Number" NFlags)
> Pin (aX aY Thickness Drill "Name" "Number" NFlags)
> Pin (aX aY Thickness Drill "Name" NFlags)
> Pin (aX aY Thickness "Name" NFlags)
> 
> The parser only sees the syntax, not the semantics:
> 
> pin_hi_format
> 		: T_PIN '[' NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER STRING STRING flags ']'
> pin_1.7_format
> 		: T_PIN '(' NUMBER NUMBER NUMBER NUMBER STRING STRING NUMBER ')'
> pin_1.6.3_format
> 		: T_PIN '(' NUMBER NUMBER NUMBER NUMBER STRING NUMBER ')'
> pin_newformat
> 		: T_PIN '(' NUMBER NUMBER NUMBER STRING NUMBER ')'
> pin_oldformat
> 		: T_PIN '(' NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER STRING STRING NUMBER ')'
> 
> What happens if I want to add another parameter?

Design the primitives right from the beginning and you won't have to. The real problem is that "pin" is obviously not a primitive concept here.

> 
> 
> _______________________________________________
> geda-user mailing list
> geda-user@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
> 

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd@xxxxxxxxx




_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user