DJ Delorie wrote:
Also, my proposal is to have the busses converted to multiple independent nets in the common parts of gnetlist, so that you don't have to tweak every single backend to add support for them. You can still support "magic" net names that the backends understand, if you want, but it seems to me a common concept like "bus" should be done in common code and be consistently applied across all the backends.
Sure, and the big EDA code based on LISP/Guile also uses syntax for names so a wire with such a name attrib seems to be all that's necessary to define a bus. Putting the syntax netname[0:7] into form netname[0], netname[1], .... for the backends is fine. Seems to me the common code would still need to be aware of bus nets. John -- ex Cadence and Mentor layer outer among other things... _______________________________________________ geda-user mailing list geda-user@xxxxxxxxxxxxxx http://www.seul.org/cgi-bin/mailman/listinfo/geda-user