On Aug 9, 2009, at 9:59 PM, A.Burinskiy wrote: > John, > > Do you mean that one day source= attribute is reference to schematic, > another day it is something else?
No, I mean that many back ends need to see a flat netlist, while in the future others will need to see the hierarchy. The ones that need to see the hierarchy will need to see the source= attributes. All of them. > We have to stick to some reasonable > meaning of all attributes, at list to be able to exchange libraries > and > collect our work over the years, isn't it? Yes. That's one reason I recommended you master the documentation for spice-sdb before writing another SPICE netlister. > Talking about ynetlist: it has exactly front, inner, and backend. I > call > it component/net collection, symbol elaboration, output netlist. By > modifying only output I may create any netlist. But yet I do not see a > reason why user should mangle with programming.... It is programmer > responsibility to cover all needs. I absolutely and emphatically disagree. Users cannot count on programmers to solve the right problems. Programmers are masters of technique, but the most important knowledge needed to make a successful program is understanding of the *application*. Users need to take that responsibility. It's similar to writing a scientific paper: a scientist must be the main author. A technical writer is very useful in the process, but not central. Programming is an essential enabling skill, similar to technical writing. Everybody should have a reasonable level of competence here. Specialist programmers are there to help produce the highest quality product, not to choose how to address the problem to be solved. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ [email protected] _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
