On Oct 20, 2007, at 1:40 AM, Peter TB Brett wrote: > Hi folks, > > I wish to propose the following compromise: > > - Implement the new embedding system (separate symbol definition and > instantiation, and checks that the embedded symbol matches the library > symbol). I don't think anyone has disputed that this is a good idea.
Nobody disputes this because hardly anybody uses embedded symbols in active designs, I think. They are broken: only good for frozen export. If you fix *that*, your proposal still leads to confusion. Right now, a symbol edit has the scope of the library that contains it, but now you'll have edits whose scope is a single file. But usually, you want the the scope to either be: 1. The whole project or 2. A single symbol. A file is a strange scope. Even many C programmers agree ;-) John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ [EMAIL PROTECTED] _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
