Yes I am doing my own thing rather then being limited by existing capabilities but I am still interested in why do one thing or another? One way that a NASA human factors researcher friend of mine approaches usability requirements is to dream up as many senerios as possible, prioritize them and grades the propossed solutions against the prioritized list. Earlier I posted such a list. If the point of the netlister is to set up the data structures in preperation for exporting them via the backend then what is accomplished post back end?
The continued existence of some feature just because it is there even if it is not used that limits or makes substantial improvements difficult doesn't make sense to me. Leaving such code in place is just another form of clutter. Unfortunantly such clutter is a hallmark of the geda code base. Unfortunantly code clutter makes code more difficult to understand and hence more difficult for others to improve. Steve Meier Ales Hvezda wrote: >> Nothing may be gained from it. However, >> since it is a feature of gnetlist, if we eliminate >> it, it would be helpful if it is clearly posted >> in gEDA-dev forum so that everyone knows >> about it. >> >> > > No worries there. Steve has forked all of gEDA/gaf and is doing > his own thing. Things like the command line flags will not be removed > from official gnetlist without some notice and/or reason. > > -Ales > > > > _______________________________________________ > geda-user mailing list > [email protected] > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user > > _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
